> Your use case is interesting in that they are almost the same
> requirements in the case of our GlassFish Appserver! GF v2 will have
> Shoal in it for this purpose.
That is the reason why I selected Shoal. I looked at ActiveCluster and
Hedera too. ActiveCluster uses JMS for group communication, which I found
too heavyweight. And Hedera lacks documentation unfortunately.
> Also, some of our plans ahead are to support state sync and caching as
> part of this generic framework. So perhaps you could consider joining
> our fledgling community as a developer contributor. You only need to
> sign Sun's Contributor Agreement to contribute code, patches or test
> cases.
Thanks. I will consider that. But note that I do not know a lot about how
clustering works. I find it very interesting though. For now I will stick
to being a user.
>> The issue tracker only has subcomponent 'www' at this moment. Can you
>> add a subcomponent for the code? Thanks.
> Done. Once you log the issue, could you point to specific code area you
> were referring to for clarity. Alternatively you could also submit a
> patch if you have time.
I filed a bug for the possibility of creating modules for the same group
with different server IDs:
https://shoal.dev.java.net/issues/show_bug.cgi?id=1
And for a new module instead of an existing one being returned for the
same group depending on the invocation order of startGMSModule:
https://shoal.dev.java.net/issues/show_bug.cgi?id=2
Please verify that what I am saying in the bugs is correct.
I will try to fix both issues and if I find a solution I will submit
patches.
Kind regards,
Johan