[
https://issues.redhat.com/browse/JGRP-2430?page=com.atlassian.jira.plugin...
]
Bela Ban commented on JGRP-2430:
--------------------------------
On a closer look, this is *not* an issue: the secret key is the same at all members, so
the GossipRouter does not need to decrypt/encrypt a message when routing it to its
destination. The destination B has the same secret key as A, and will therefore be able to
decrypt a message encrypted by A.
GossipRouter: more efficient routing
------------------------------------
Key: JGRP-2430
URL:
https://issues.redhat.com/browse/JGRP-2430
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Major
Fix For: 5.1
GossipRouter supports both NIO (ByteBuffer) and TCP (stream-based) connections. In both
cases, however, the entire message is read and then routed to the destination address.
It would be better to only read the cluster name and target address, and then use
efficient stream-to-stream (or channel-to-channel) _transfer mechanisms_, which avoids
temporary copies of data and the full reading of messages.
Also look into routing of entire message _batches_.
Investigate whether this is possible.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)