[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-699) Ensure remoting implements true asynchronous callbacks

[Ovidiu Feodorov (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-699?page=all ]

Ovidiu Feodorov closed JBMESSAGING-699.
---------------------------------------

    Resolution: Done

Remoting 2.2.0.Alpha6 implements "true" asynchronous invocations, in that the client invoker writes the invocation on the socket's output stream and returns immediately without reading anything from the input stream. Same on server-side, nothing is written on the socket in response to a oneway invocation. Same for oneway callbacks.

There's no easy way of writing a test to automatically check this, however I added PureAsynchronousCallTest.testAsynchronousDirectCall(), testAsynchronousCallback() that could be handy to experiment with oneway invocations.

I've converted synchronous to asynchronous invocations in those two cases mentioned above: server-to-client sending messages (ServerConsumerEndpoint.handle()) and client-to-server flow control (DelegateSupport.invoke(), for "changeRate()"

> Ensure remoting implements true asynchronous callbacks
> ------------------------------------------------------
>
>                 Key: JBMESSAGING-699
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-699
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Ovidiu Feodorov
>            Priority: Blocker
>             Fix For: 1.2.0.Beta2
>
>
> We need to chase remoting to make sure they implement true asynchronous invocations.
> We need these for delivering messages from the server to the client, and for sending certain invocations from client to server.
> Without this, performance will greatly suffer.
> A "true" asynchonous callback is where the invocation is written to the transport using the same thread as the invoking thread, and returns immediately.
> It does not wait to read a response, and it just execute a normal invocation using a thread from a pool and discard the result.

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