How does SoapHttpClientProtocol.InvokeAsync work?

Question

I am looking for more information on how the SoapHttpClientProtocol.InvokeAsync method call works and the completed event and threading.  Does this create a new thread that all requests get executed on?  How many concurrent requests can be made at one time?  How well does this method work if the web service is known to be slow and sending many requests?  What are the performance issues with calling this method?  Are there any ways to tweak the settings to have this perform better?   When does the actual call to the web service go out?  Any other information on this works would be helpful.  This is being called from within a Windows Service as well and is written in .NET 4.0 running on Windows 2008 servers.

Final question, should I upgrade this code to the WCF and are there any good examples of a WCF client calling a java soap web service?  I am looking for something that will perform well under heavy load since the web service I am calling willl take serval seconds to respond.

Answer 1

Hello,

Follow the links below to get the basic idea.

http://msdn.microsoft.com/en-us/library/system.web.services.protocols.soaphttpclientprotocol.invokeasync.aspx

http://www.codeproject.com/Articles/14662/Access-Web-Services-Asynchronously-in-NET-Design-P