----- Original Message ----- From: "Anne Thomas Manes" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 31, 2003 06:30 Subject: RE: Antw: Asynchronous interface
> There's a difference between an asynchronous API and an asynchronous > transport. You should be able to make asynchronous calls over HTTP, too. > > For a description of what I man, see the WASP documentation on asynchronous > API: > http://www.systinet.com/doc/wasp_jserver/basics/webServiceInvocation.html#ba > sics.webServiceInvocation.asynchronous Well, axis CVS has a modified tcp mon that can simulate delays, so you can see how bad synchronous soap calls are if you do them in your primary thread. There is nothing in axis1.1 for async soap, but I could imagine something like -A thread reading off a Queue of Call objects, making each one in turn -calling some call-specific listener with progress as it goes -calling the listener with the response when it finishes -leaving the listener to deal with the response But I need to experiment with a special case of this (big file upload) to see if it flies
