[
http://jira.jboss.com/jira/browse/JBREM-324?page=comments#action_12379624 ]
David Lloyd commented on JBREM-324:
-----------------------------------
The Routing/Discovery API of Remoting 3 should facilitate this ability, if I understand
correctly. It will maintain a list of paths to endpoints, and choose the best one
available at any given time.
Facility for real-time decision on best InvokerLocator by which to
contact a given handler.
-------------------------------------------------------------------------------------------
Key: JBREM-324
URL:
http://jira.jboss.com/jira/browse/JBREM-324
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.Beta1
Reporter: Ron Sigal
Assigned To: Ron Sigal
Priority: Minor
Fix For: 4.0.0.Beta1
The basic idea is to be able to communicate with a single handler by way of different
InvokerLocators. For example, if you're working over the internet, compression might
be advantageous, but if you're local it might not be. So you could have two
Connectors sharing a handler, one using the compression marshaller and one not.
How about a client that
1. gets the InvokerLocators for all of the Connectors for a certain handler, via a
detector,
2. sends some sample invocations to each and times them, and
3. displays the results.
It could be used for real time decision making or to collect information for a set of
rules.
--
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