[jboss-jira] [JBoss JIRA] Updated: (JGRP-176) Asynchronous dispatching of requests in RequestCorrelator

Bela Ban (JIRA) jira-events at lists.jboss.org
Tue Mar 13 12:09:47 EDT 2007


     [ http://jira.jboss.com/jira/browse/JGRP-176?page=all ]

Bela Ban updated JGRP-176:
--------------------------

    Fix Version/s: 2.6
                       (was: 2.5)

Moved to 2.6, as break-the-locks (JBCACHE-326) has been moved to JBossCache 2.1.0.

Note: we may not even need this functionality anymore, as the concurrent stack might already solve this by delivering messages from different senders on different threads

> Asynchronous dispatching of requests in RequestCorrelator
> ---------------------------------------------------------
>
>                 Key: JGRP-176
>                 URL: http://jira.jboss.com/jira/browse/JGRP-176
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.2.9.1, 2.2.9, 2.2.8
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> In RequestCorrelator.handleRequest(), we call handle(Message) on the registered RequestHandler (RpcDispatcher in the case of JBossCache).
> Because of http://jira.jboss.com/jira/browse/JBCACHE-326, we need to provide an asynchronous way of calling handle(Message), which doesn't need to wait for the call to return, but is notified later when the response is ready (or not at all if the call is asynchronous).
> This could be implemented using a subinterface of RequestHandler (e.g. AsyncRequestHandler), and a *future*.

-- 
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

        



More information about the jboss-jira mailing list