On 25-09-12 06:11, Greg Trasuk wrote:
My thought is that you'd package one or more of these classes in a jar file (service archive, or ".sar"?) and deploy it to the service container. Much like in EJB3, the container would scan the jar file for deployable services, and export, then register them in the appropriate join group. It could continue to use the
Do you see the server part and client part strongly separated? i mean, i would like to keep a peer-to-peer style class like Federation, but underneath, a ServiceContainer and Client class?
-- QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
