Hi Jose

Thanks for the reference to the paper - when using jxta I'm having to take into account node failure and clients are generally aware of which nodes have the database - jxta is pretty good at discovery. This idea is to ensure that clients connect to the 'best' connection at the time an operation is invoked. The 'load balancing' is effectively taking place on the client side.

The license is an issue do to the fact that customers may construct standalone applications using my libraries, your libraries and all the other libraries which they might pass onto their clients. Some customers may not not want to make public the source of their application. Other customers may be overlook the gpl issue, distribute an application without source and be unaware that they are contravening escadas license terms, and as a consequence be liable. All of the libraries I'm using, including my own (once they are ready), hibernate, jboss, jxta, derby etc have at worst the lgpl license, and at best the apache license.

I dearly hope we can resolve this licensing issue.

As for the client node and load balancing, I think that this is going to need some more thought.

Cheers
Nick

---

Are you the Quizmaster? Play BrainBattle with a friend now!