[
https://issues.apache.org/jira/browse/OAK-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998168#comment-15998168
]
Robert Munteanu commented on OAK-6136:
--------------------------------------
[~tomek.rekawek] - no need to wait for my vote :-) I was mostly offline anyway
so that would've been quite hard.
{quote}In our case, the existing service is a node store and each of them has
to be a fully functional and working implementation.{quote}
That is where I think the difference lies between our views. For me a partially
populated node store, even though technically fully functional, is not usable
from a client perspective. Only when multiple node store mounts are put
together can they be exposed. Consider a Sling application with two mounts:
- /libs and /apps
- everything else
Even though both mounts are available to be used independently, they don't make
sense in isolation. The /libs and /apps mount has no content to serve, while
the main mount does not know how to serve content. Only when put together do
they work as intended.
So I am worried that advertising that Oak supports 'federation' will lead to
confusion and to false expectations regarding what this feature actually does.
Another point on multiplexing vs federation - federation is a high-level
concept while multiplexing is a low-level one - which matches the level of our
implementation - the NodeStore work we've done is quite low-level. I am not
attached to multiplexing, but I don't think federation is the right term here.
Mabye we can try and ask on oak-dev for more ideas?
> Extract the multiplexing implementation code into a separate bundle
> -------------------------------------------------------------------
>
> Key: OAK-6136
> URL: https://issues.apache.org/jira/browse/OAK-6136
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: federated
> Reporter: Robert Munteanu
> Assignee: Julian Sedding
> Fix For: 1.7.0, 1.8
>
> Attachments:
> 0001-OAK-6136-Extract-the-multiplexing-implementation-cod.patch,
> OAK-6136.patch
>
>
> Since we already kicked off the m12n effort for 1.8 it would be good to
> separate the multiplexing implementation from oak-core into its own bundle as
> well.
> I will look into providing a patch for the change.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
