You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2014/02/07 12:05:20 UTC

[jira] [Updated] (SLING-3377) Make topology connector a plain HttpServlet instead of a SlingServlet

     [ https://issues.apache.org/jira/browse/SLING-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Egli updated SLING-3377:
-------------------------------

    Fix Version/s: Discovery Impl 1.0.4

> Make topology connector a plain HttpServlet instead of a SlingServlet
> ---------------------------------------------------------------------
>
>                 Key: SLING-3377
>                 URL: https://issues.apache.org/jira/browse/SLING-3377
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Discovery Impl 1.0.2
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: Discovery Impl 1.0.4
>
>
> Currently the TopologyConnectorServlet is registered as a SlingServlet, thus using the entire set provided, such as authorization, resource resolution etc. Besides using unnecessary CPU cycles, this also results in too much logging.
> The connector servlet should be changed to be registered as a plain HttpServlet instead.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)