On Mon, Dec 2, 2013 at 5:06 PM, Angela Schreiber <[email protected]> wrote: > just one more addition: > > IMHO it was fairly straight forward to implement the server side > part of the jcr-remoting based on OAK. that would fit pretty much what > was always listed as 'native' implementation in the jackrabbit > documentation (and which was always marked with a dotted lined). > that was for sure much better than having yet another JCR layer > on the server side.
that's great. However, I would have thought there is a stricter separation between JCR2SPI and SPI2CORE. AFAICT, in Oak it looks more like there is a JCR2CORE and a DAVEX2CORE. And the SPI is merely a bucket we throw all the API in that are not pure client APIs. It might be more clear to use oajo.client.* and oajo.server.* then... regards, toby > > angela > > On 12/2/13 12:38 PM, "Jukka Zitting" <[email protected]> wrote: > >>Hi, >> >>On Mon, Dec 2, 2013 at 6:34 AM, Tobias Bocanegra <[email protected]> >>wrote: >>> so this means, that the SPI as we had it in Jackrabbit 2.x does no >>> longer exist. And that if we want to continue to support remoting via >>> DavEx (for example) users need to use the (client) code from >>> Jackrabbit. >> >>Exactly. >> >>BR, >> >>Jukka Zitting >
