Sacha Labourey wrote:
> Nevertheless, as you probably know, when doing clustering we also need some
> "advanced" communication semantics. We need to be able to know which message
> has been received by which member in which order (for example). A cluster
> where invocations cannot be received in the same order by each node, when
> you do not know which node has received which message, ... is not a very
> usefull cluster IMHO.
You are making way too many assumptions about how to implement the
cluster here. There is no inherent need for what you describe.
> And this is JavaGroups job. JG provides memberhip
> protocol, state transfer protocol, group views, group communication, ... JG
> also provides a kind of discovery ;) : you create a group with a particular
> name, and you then are able to use extended communication semantic in the
> group, get state transfer events, membership events, ...
There is a lot of complexity inherent in what you describe above. I
doubt that most of that will be useful. And I'm assuming we're talking
about clustering the EJB container here. For the JMS stuff the above
will be more interesting.
KISS.
> (because we do need this communication semantic).
Can you explain why and where this is needed? It seems like this depends
on a particular implementation strategy.
/Rickard
--
Rickard Öberg
Software Development Specialist
xlurc - Xpedio Linköping Ubiquitous Research Center
Author of "Mastering RMI"
Email: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
