Hi, Thank you for the feedback.
On 20.11.2017 21:32, Woonsan Ko wrote: > On Mon, Nov 13, 2017 at 9:44 AM, Ioan Eugen Stan <[email protected]> wrote: >> Hello, >> >> I wish to explore with the list the possibility of having an >> implementation for JCR/Oak API based on GRPC (or another similar RPC >> framework with lots of client bindings like FlatBuffers, etc). >> >> From my point of view, the main benefits of having such an >> implementation are that clients from a lot of languages can easily >> interact with the JCR repository remotely. I think the initial >> implementation should just wrap the current Java API. > JCR API is non-RPC-friendly, stateful in object hierarchy and event > publish-subscription dependent, so it might be not easy to do that > way. > >> Having this feature would allow a plethora of languages to consume a JCR >> repository as an SQL database. > Jackrabbit has a built-in JCR API support over WebDAV protocol. See > the "JCR Webdav Server" section and its protocol specification > document. [1] > I heard some people take advantage of the feature for their PHP > clients ("PHPCR"), too. > Anyway, if the main goal is to widen the language support, this can be > another option to consider. > > Just my two cents, > > Woonsan > > [1] http://jackrabbit.apache.org/jcr/components/jackrabbit-jcr-server.html > >> Again, this proposal is meant to be a mental exercise. >> >> Looking forward to hearing your thoughts about this, >> >> Eugen. >> >> >> Regards, >> >> >>
signature.asc
Description: OpenPGP digital signature
