Hi,
I agree with Felix. I don't currently see a need for Sling to bypass the
JCR API. If that would be needed, there is something wrong with the JCR
API or the JCR implementation.
About indexing:
Another potential Sling extension would be a custom Oak index provider
for optimizing the kinds
On Thu, Jul 5, 2012 at 12:19 PM, Thomas Mueller muel...@adobe.com wrote:
About indexing:
Another potential Sling extension would be a custom Oak index provider
for optimizing the kinds of queries Sling uses.
I'm not sure what you mean here. I don't see Sling having it's own index
Hi,
On Wed, Jul 4, 2012 at 5:43 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
On Wed, Jul 4, 2012 at 5:35 PM, Stefan Guggisberg
stefan.guggisb...@gmail.com wrote:
On Wed, Jul 4, 2012 at 2:37 PM, Michael Dürig mdue...@apache.org wrote:
- HTTP bindings (OAK-103, OAK-104)
* Provide
Hi,
I'm not sure what you mean here. I don't see Sling having it's own index
*mechanism*. Probably Sling will need specific indexes, but that's just
configuration, and not implementation (code)...
Being able to integrate totally different indexing mechanisms can be
useful if Oak can provide
On Wed, Jul 4, 2012 at 2:37 PM, Michael Dürig mdue...@apache.org wrote:
Hi,
Last week some of us met for another small Oakathon in Basel. Below is a
list of topics that where touched and worked on and the related Jira issues.
Any additional input is appreciated.
- Observation (OAK-144):
Hi,
On Wed, Jul 4, 2012 at 5:35 PM, Stefan Guggisberg
stefan.guggisb...@gmail.com wrote:
On Wed, Jul 4, 2012 at 2:37 PM, Michael Dürig mdue...@apache.org wrote:
- HTTP bindings (OAK-103, OAK-104)
* Provide extension points for Sling to hook into. (See also the
i don't remember any
2012/7/4 Jukka Zitting jukka.zitt...@gmail.com:
Hi,
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
