I got chance to have a mini-hackathon with some geronimo committers
over the weekend to hack up a real simple client API to some kind of
state store, which could be clustered, that the OpenEJB, ServiceMix,
Lingo and Tuscany guys could use.
Rather than focussing on the possible technical implementations and
techniques (like group communication, election strategies,
distributed locking, totem protocol, distributed hash maps etc) we
tried to put in place a simple client API for the person who has to
integrate some kind of client session state into the client/server
side of OpenEJB or ServiceMix etc .
Its a very simple API and should be trivial to implement in a
gazillion of different ways (a HashMap, totem, WADI, just a database
or file system, a combination of database for being the controller &
using point to point non-reliable messaging with the other members to
group election strategies etc). Without further ado here's where it
lives...
http://svn.apache.org/repos/asf/geronimo/trunk/modules/session/
There's some javadoc that tries to explain the use cases, the design
goals behind the client API and a variety of possible implementations
we could do - the idea is based on your requirements and performance
targets you may use a real simple implementation or a wacky complex
one. We tried to assume a possibly low QoS (e.g. 1 box with a
HashMap) while allowing any implementation to plug in based on its
requirements.
Here's more docs in HTML which explains it much better....
http://svn.apache.org/repos/asf/geronimo/trunk/modules/session/src/
java/org/apache/geronimo/session/package.html
Thoughts?
To the WADI folks - do you think it'd be easy to put WADI underneath
this API?
James
-------
http://radio.weblogs.com/0112098/
James
-------
http://radio.weblogs.com/0112098/
