[
http://jira.jboss.com/jira/browse/JGRP-105?page=comments#action_12371759 ]
Galder Zamarreno commented on JGRP-105:
---------------------------------------
Looking at JBCACHE-816, I spotted some potential requirements
for JGRP-105 as explained in:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073104#...
Note: DC refers to Data Centre as indicated in
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAcrossDataCentres
Summarised requirements:
- be able to filter which traffic get's propagated to DCs, i.e. only JBC
CRUD methods (put, remove...etc). JGroups could define an interface
for that, which JBC would implement based on its requirements.
- configurable (sync/async) communications for in DC (typically IP multicast and
synchronous) and inter DC (inter GR - typically TCP based and asynchronous)
- GR failover. We need to support failover of a GR so that another node in the
local DC takes over.
GossipRouter should additionally listen on IP multicast group and
bridge traffic
--------------------------------------------------------------------------------
Key: JGRP-105
URL:
http://jira.jboss.com/jira/browse/JGRP-105
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.2.8
Reporter: Bela Ban
Assigned To: Vladimir Blagojevic
Fix For: 2.6
GossipRouter should be augmented to not just route traffic between TCP endpoints, but
also between an IP multicast group and all TCP endpoints.
It should be configured with the properties for a (multicast-based) group X, and then
forward messages from X to all of its attached endpoints, and vice versa.
In the future, this concept could be extended to generic bridging functionality, which
will allow to construct hierarchical messaging trees, similar to the MBone
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira