You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/10/03 10:06:33 UTC

[jira] Created: (SLING-1816) Make Sling POST Servlet dynamically configurable

Make Sling POST Servlet dynamically configurable
------------------------------------------------

                 Key: SLING-1816
                 URL: https://issues.apache.org/jira/browse/SLING-1816
             Project: Sling
          Issue Type: Improvement
          Components: Servlets
            Reporter: Felix Meschberger


Currently the SlingPostServlet is a regaular DS 1.0 component which is stopped and restarted for updated OSGi configuration. This gives a certain amount of down-time during configuration update and also places some load on the system.

To make configuration updates as transparent and low latency as possible, it would probably be good support the new DS 1.0 functionality for dynamic configuration update using the "modify" method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SLING-1816) Make Sling POST Servlet dynamically configurable

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated SLING-1816:
-------------------------------------

    Fix Version/s: Servlets Post 2.1.2

Tentatively scheduling for post 2.1.0 release along with SLING-1725

> Make Sling POST Servlet dynamically configurable
> ------------------------------------------------
>
>                 Key: SLING-1816
>                 URL: https://issues.apache.org/jira/browse/SLING-1816
>             Project: Sling
>          Issue Type: Improvement
>          Components: Servlets
>            Reporter: Felix Meschberger
>             Fix For: Servlets Post 2.1.2
>
>
> Currently the SlingPostServlet is a regaular DS 1.0 component which is stopped and restarted for updated OSGi configuration. This gives a certain amount of down-time during configuration update and also places some load on the system.
> To make configuration updates as transparent and low latency as possible, it would probably be good support the new DS 1.0 functionality for dynamic configuration update using the "modify" method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.