[
http://jira.jboss.com/jira/browse/JBREM-641?page=comments#action_12364644 ]
Ron Sigal commented on JBREM-641:
---------------------------------
CallbackPoller synchronizes the shutdown process so that CallbackPoller.stop() will not
return until (1) Client.getCallbacks() has returned, (2) all retrieved callbacks have been
passed to the application, and (3) and acknowledgements have been sent. In blocking mode,
though, waiting for Client.getCallbacks() to return could be very time consuming -
several seconds, for example. CallbackPoller has a new parameter, configurable by passing
in CallbackPoller.SYNCHRONIZED_SHUTDOWN (actual value "doSynchronizedShutdown").
In a synchronized shutdown, CallbackPoller.stop() will wait for Client.getCallbacks() to
return, and in an unsynchronized shutdown, it will not.
In blocking mode, the default is to do an unsynchronized shutdown, and in nonblocking
mode, the default is to do a synchronized shutdown.
re-implement the callback polling for http transport to reduce
latency
----------------------------------------------------------------------
Key: JBREM-641
URL:
http://jira.jboss.com/jira/browse/JBREM-641
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Components: callbacks
Affects Versions: 2.0.0.GA (Boon)
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
Per forum thread, would be nice to have a more "real-time" way to get callbacks
from server when using http transport so don't have to wait on ping period.
--
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