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 2015/12/30 11:20:49 UTC

[jira] [Assigned] (SLING-5265) Rethink the current api

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

Carsten Ziegeler reassigned SLING-5265:
---------------------------------------

    Assignee: Carsten Ziegeler

> Rethink the current api
> -----------------------
>
>                 Key: SLING-5265
>                 URL: https://issues.apache.org/jira/browse/SLING-5265
>             Project: Sling
>          Issue Type: Sub-task
>          Components: API, JCR, ResourceResolver
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Resource 2.6.0, API 2.10.0, Resource Resolver 1.3.0
>
>
> I've started different threads in the dev list, whether the current api is good or could be changed. The three main points are:
> - how to deal with external events
> - should we add pattern/globbing support for listeners
> - should we merge the resource provider events into the resource events
> We should update this issue based on the results of the discussions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)