[ http://jira.jboss.com/jira/browse/JGRP-36?page=history ]
Bela Ban resolved JGRP-36:
--------------------------
Resolution: Done
Implemented as MPING. Stack would be for example TCP:MPING, check
JGroups/conf/mtcp.xml for an example.
MPING uses its own IP multicast socket to send and receive discovery
requests/responses. Can be used in
* conjuntion with a non-UDP transport, e.g. TCP.<p>
* The discovery is <em>assymetric</em>: discovery requests are broadcast via
the multicast socket, and
* received via the multicast socket by everyone in the group. However, the
discovery responses are sent
* back via the regular transport (e.g. TCP) to the sender (discovery request
contained sender's regular address,
* e.g. 192.168.0.2:7800).
> TCP:PING, TCP transport combined with multicast discovery
> ---------------------------------------------------------
>
> Key: JGRP-36
> URL: http://jira.jboss.com/jira/browse/JGRP-36
> Project: JGroups
> Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 2.2.8
>
>
> Use IP multicast for discovery/merging, but TCP for transport
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/info/Sentarus/hamr30
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
