summaryrefslogtreecommitdiffstats
path: root/sca-java-2.x/trunk/modules/endpoint-hazelcast (unfollow)
Commit message (Collapse)AuthorFilesLines
2010-01-08Change the Hazelcast registry to support both distributed an in-VM only ↵antelder2-6/+16
operation git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@897140 13f79535-47bb-0310-9956-ffa450edef68
2010-01-06Refine MFrfeng1-2/+2
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@896656 13f79535-47bb-0310-9956-ffa450edef68
2010-01-06Updates to the Hazelcast regsitry manifestantelder1-16/+7
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@896648 13f79535-47bb-0310-9956-ffa450edef68
2010-01-05More changes to get the Hazelcast endpoint registry workingantelder7-578/+560
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@896269 13f79535-47bb-0310-9956-ffa450edef68
2010-01-05Start a endpoint registry based on Hazelcast. Hazelcast seems to do just ↵antelder6-0/+826
about everything we need and seems quite easy to use compared to other options. It supports multicast and explicit ip addresses, with ip addresses you only need to specifiy the address of one node and then all other nodes get notified about the new node. Hazelcast has various encryption options to secure the domain, and it has a way to have endpoints removed when a node disapears (though that requires a bit of code on our part to get to work). One limitation is currently it doesnt support multiple nodes using multicast, but they've said they can fix that. git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@896038 13f79535-47bb-0310-9956-ffa450edef68