Hi, On Wed, Jul 4, 2012 at 5:35 PM, Stefan Guggisberg <[email protected]> wrote: > On Wed, Jul 4, 2012 at 2:37 PM, Michael Dürig <[email protected]> wrote: >> - HTTP bindings (OAK-103, OAK-104) >> * Provide extension points for Sling to hook into. (See also the > > i don't remember any discussions that sling should be using > an alternative interface to access the repository. IMO > sling should only use the jcr api.
It came up as a potential option that Sling might be interested in. For example, many Sling components are currently having a hard time with the JCR observation feature, and giving them access to lower level features in Oak (or alternatively implementing the relevant Sling features directly as an Oak plugin) could simplify things a lot. Another potential Sling extension would be a custom Oak index provider for optimizing the kinds of queries Sling uses. BR, Jukka Zitting
