jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jukka Zitting <jukka.zitt...@gmail.com>
Subject Remoting granularity (Was: [jira] [Commented] (OAK-80) Implement batched writing for KernelNodeStore)
Date Wed, 02 May 2012 15:26:03 GMT

[new thread, since this is a broader issue than OAK-80]

On Wed, May 2, 2012 at 4:50 PM, Thomas Mueller (JIRA) <jira@apache.org> wrote:
> The question is how would you build an an efficient oak-core remoting, if every
> Node.setProperty requires a TCP/IP roundtrip, because it goes through oak-core
>  and down to oak-mk?

Good question.

Instead of always mapping method calls directly to remote roundtrips
(like for example JCR-RMI does), batching and caching of content
should be up to the remoting implementation to deal with.

I don't think such concerns should be baked in to the Oak API (or the
MK for that matter), as no single solution will work for all clients
and deployment scenarios. For example, it makes little sense for a
local client to have to batch changes in memory or on some custom disk
location just because doing so is necessary for a remoting layer.


Jukka Zitting

View raw message