Hello, having a mixed java - C++ implementation leads to the following (abridged version):
pros: - ease of maintenance; - compactness and organic architecture of the project, cons: - less portability; - building complexity and distribution; However these choices can be postponed to the design stage as for now we need to define basic clustering requirements. As food for thought, I'd suggest: - clustering for dependability: pretty obvious; - clustering and performance: which trade-offs ? - clustering adaptability: at which level ? - adaptability policies: none / some / mid - smart / "zero policy (a.k.a ad hoc control theory)" / autonomic ? Can we start a whiteboard discussion on this ? Cheers, Etienne On Wed, Mar 11, 2009 at 2:55 PM, Gordon Sim <[email protected]> wrote: > Alan Conway wrote: >> >> I don't think that writing a virtual synchrony implementation from scratch >> is the right way to go. >> >> I'd be strong there any existing open-source virtual synchrony solutions >> for Java? > > "EVS4J is a pure-Java(tm) implementation of the Totem single ring protocol" > > http://code.google.com/p/evs4j/ > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
