You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2009/07/02 07:44:47 UTC
[jira] Created: (SLING-1029) Disable development mode by default
Disable development mode by default
-----------------------------------
Key: SLING-1029
URL: https://issues.apache.org/jira/browse/SLING-1029
Project: Sling
Issue Type: Improvement
Components: Scripting JSP
Affects Versions: Scripting JSP 2.0.4
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: Scripting JSP 2.0.6
Currently the development mode is turned on by default for the JSP scripting handler. This mode has a dramatic decrease of performance as on every request the jsp is checked for modifications. As the defaults should be sensible defaults for production as well, we should turn off development mode. The jsps are checked for modifications every 4 seconds anyway, so in practice this shouldn't make any difference for development.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1029) Disable development mode by default
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-1029.
-----------------------------------
Resolution: Fixed
Changed default in Revision: 790463 to false.
> Disable development mode by default
> -----------------------------------
>
> Key: SLING-1029
> URL: https://issues.apache.org/jira/browse/SLING-1029
> Project: Sling
> Issue Type: Improvement
> Components: Scripting JSP
> Affects Versions: Scripting JSP 2.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Scripting JSP 2.0.6
>
>
> Currently the development mode is turned on by default for the JSP scripting handler. This mode has a dramatic decrease of performance as on every request the jsp is checked for modifications. As the defaults should be sensible defaults for production as well, we should turn off development mode. The jsps are checked for modifications every 4 seconds anyway, so in practice this shouldn't make any difference for development.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1029) Clarify Configuration Properties
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-1029:
------------------------------------
Summary: Clarify Configuration Properties (was: Disable development mode by default)
> Clarify Configuration Properties
> --------------------------------
>
> Key: SLING-1029
> URL: https://issues.apache.org/jira/browse/SLING-1029
> Project: Sling
> Issue Type: Improvement
> Components: Scripting JSP
> Affects Versions: Scripting JSP 2.0.6
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Scripting JSP 2.0.8
>
>
> Currently the development mode is turned on by default for the JSP scripting handler. This mode has a dramatic decrease of performance as on every request the jsp is checked for modifications. As the defaults should be sensible defaults for production as well, we should turn off development mode. The jsps are checked for modifications every 4 seconds anyway, so in practice this shouldn't make any difference for development.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1029) Clarify Configuration Properties
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-1029.
-----------------------------------
Resolution: Fixed
Changed the title for this issue and enable development mode again, remove unused reload property, change property order and clarify properties a little bit.
> Clarify Configuration Properties
> --------------------------------
>
> Key: SLING-1029
> URL: https://issues.apache.org/jira/browse/SLING-1029
> Project: Sling
> Issue Type: Improvement
> Components: Scripting JSP
> Affects Versions: Scripting JSP 2.0.6
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Scripting JSP 2.0.8
>
>
> Currently the development mode is turned on by default for the JSP scripting handler. This mode has a dramatic decrease of performance as on every request the jsp is checked for modifications. As the defaults should be sensible defaults for production as well, we should turn off development mode. The jsps are checked for modifications every 4 seconds anyway, so in practice this shouldn't make any difference for development.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (SLING-1029) Disable development mode by default
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler reopened SLING-1029:
-------------------------------------
Actually my findings have been a little bit wrong - if development mode is turned off, reloading is disabled completely
> Disable development mode by default
> -----------------------------------
>
> Key: SLING-1029
> URL: https://issues.apache.org/jira/browse/SLING-1029
> Project: Sling
> Issue Type: Improvement
> Components: Scripting JSP
> Affects Versions: Scripting JSP 2.0.6
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Scripting JSP 2.0.8
>
>
> Currently the development mode is turned on by default for the JSP scripting handler. This mode has a dramatic decrease of performance as on every request the jsp is checked for modifications. As the defaults should be sensible defaults for production as well, we should turn off development mode. The jsps are checked for modifications every 4 seconds anyway, so in practice this shouldn't make any difference for development.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.