apache-tuscany - apache tuscany

	Commit message (Collapse)	Author	Age	Files	Lines
*	Expose system definitions from the deployer	rfeng	2010-01-19	1	-51/+82
\| \| \| \| \| \| \|	Add the removal of entries when the member leaves the group Add listeners to the hazelcastInstance git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@900661 13f79535-47bb-0310-9956-ffa450edef68
*	Change the Hazelcast registry to support both distributed an in-VM only ↵	antelder	2010-01-08	2	-6/+16
\| \| \| \| \| \|	operation git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@897140 13f79535-47bb-0310-9956-ffa450edef68
*	More changes to get the Hazelcast endpoint registry working	antelder	2010-01-05	4	-577/+451
\| \| \| \|	git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@896269 13f79535-47bb-0310-9956-ffa450edef68
*	Start a endpoint registry based on Hazelcast. Hazelcast seems to do just ↵	antelder	2010-01-05	2	-0/+577
	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