[
https://issues.redhat.com/browse/JGRP-1424?page=com.atlassian.jira.plugin...
]
Bela Ban commented on JGRP-1424:
--------------------------------
I'm questioning the usefulness of having multiple transports, against the added
complexity...
If we have IP multicasting available, we'd probably use UDP:PING (or TCP:MPING if we
don't want to use IP multicasting for sending/receiving of messages, only for
discovery).
If IP multicasting is disabled, we'd have to use TCP anyway.
I currently don't see a use case where both UDP *and* TCP would be enabled...
TP: use of multiple transports
------------------------------
Key: JGRP-1424
URL:
https://issues.redhat.com/browse/JGRP-1424
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Major
Fix For: 5.1
Refactor TP so that the socket sending and receiving is done in a separate class (UDP,
TCP, TCP_NIO). Once this is done, add the ability to attach multiple transports to TP,
e.g. UDP and TCP.
The UDP transport could then be used for cluster wide messages (null destination) and the
TCP transport could be used for unicast messages (non-null destination).
Or this could be overridden by a message flag on a per-message basis !
We could even attach multiple transports of the same type, e.g. one per physical network
(10.x.x.x and 192.168.x.x), and do round-robin sending over them.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)