jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Reschke <julian.resc...@gmx.de>
Subject Re: Native HTTP bindings for Oak
Date Wed, 27 Jun 2012 13:07:57 GMT
On 2012-06-27 14:57, Stefan Guggisberg wrote:
> for once i'm a 100% with felix ;)
>
> if i understand jukka's proposal correctly, it's about promoting an alternative
> public client api. in my understanding the ultimate goal of the oak project
> is to come up with a highly efficient & scalable jcr implementation.
> imo we should focus on this goal.
>
> i thought that we have a consensus of how the oak stack should be layered, i.e.
>
> app / sling / oak-jcr (trans. space) / [remoting /] oak-core [remoting
> /] oak-mk.
>
> now your proposal seems to imply a different architecture...
> ...

I would say that the approach to expose a different 
branch/revision/activity/session/whatever in a different URI space is 
completely orthogonal to the question whether we do OAK-over-HTTP or 
JCR-over-HTTP. And also, that is a good idea :-)

Best regards, Julian

Mime
View raw message