4 - Asynchronous with Future Start: Sun Nov 24 19:42:42 IST 2013
4 - Asynchronous with Future End: Sun Nov 24 19:42:42 IST 2013
Async Source Payload Response = <ns2:addResponse xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns2="http://arith/"><return>31</return></ns2:addResponse>
- 4.1 simulating async work
4 - Asynchronous request with Future respondet at: Sun Nov 24 19:42:43 IST 2013 with Response
a sarkar wrote:Abhay,
Why do you need to poll (while (!f.isDone())) if you've configured a callback handler? The main thread shouldn't care whether the server has responded or not because that defeats the purpose of asynchrony. Seems like a mix of both request-and-poll and request-and-register async variations.
Abhay Agarwal wrote:If I do not do that , my code in Async Handler do not get called.
So How I achieve same functionality without f.isDone condition ?
Asynchronous call Starts: Mon Nov 25 21:53:09 CET 2013
Client continues other work
Client decides to check the result Mon Nov 25 21:53:18 CET 2013 with Response
<ns2:addResponse xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns2="http://arith/"><return>25</return></ns2:addResponse>
Afra Tamam wrote:What is your server code?
Himai Minh wrote:I do not see the main difference between the callback and polling mechanisms.
It seems to me that callback uses a handler to check the status of the response. But polling does not use a handler to check the status. In polling, the client gets the response directly and the client checks if the response is complete or not.