[
https://jira.jboss.org/jira/browse/JGRP-1177?page=com.atlassian.jira.plug...
]
Paul Ferraro updated JGRP-1177:
-------------------------------
Attachment: patch.txt
Proposed patch expanding on the sample implementation with the following changes:
* Refactored pieces into separate classes with nicer names
* ScopedRpcDispatcher registers its scope with a ScopedUpHandler
* Added ScopeUpHandler deregistration on ScopedRpcDispatcher.stop().
* ScopedUpHandler accepts an optional default handler, which will be triggered for
non-message events or messages with no scope header
* ScopedUpHandler returns NoHandlerForScope object if message is received for an unknown
scope (e.g. its handler was not yet registered or was already deregistered)
* Automatically adds RspFilter to RequestOptions that rejects NoHandlerForScope responses,
decorating any existing filter, if necessary.
* Added ScopedMessageDispatcher analogue
Multiple components using the same channel
------------------------------------------
Key: JGRP-1177
URL:
https://jira.jboss.org/jira/browse/JGRP-1177
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.10
Attachments: bla2.java, patch.txt
Investigate sharing a channel between multiple components. Unlike the Multiplexer, this
is light weight and doesn't require service views or other kludges !
Attached is an example of how this could be implemented.
This JIRA is only to investigate whether being able to share a channel between multiple
components makes sense, or whether a shared transport is better suited. We do NOT want to
re-create the Multiplexer, which to this day still haunts me !
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira