[
https://issues.apache.org/jira/browse/OAK-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994618#comment-15994618
]
Robert Munteanu commented on OAK-6136:
--------------------------------------
I am not sure that federation is the proper term for what we currently have (
and also for what we want to have ) in Oak.
Federation to me see to be about different services becoming interoperable More
importantly I think it's about existing services that work in a standalone
fashion but can also work together - in a federated mode. See
- https://dev.mysql.com/doc/refman/5.7/en/federated-storage-engine.html
- https://en.wikipedia.org/wiki/Federated_database_system
In our scenario the mounts - those which we assemble - are not really usable by
themselves as they only contain a part of the repository.
I think multiplexing is a better metaphor. It originally was about combining
multiple signals into a single one. I have no experience with
telecommunications so I won't comment on that but for me the concept of
combining multiple parts into a larger one is closer to what we offer with our
implementation.
So yes, naming is tricky, multiplexing is maybe not the best option, but I
think federation gets us further from what we actually do.
> 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)
