CODEWITHSUNDEEP
asp.netsslweb-services
Kevin
Kevin

Reputation: 13

Calling web services from ASP.NET application and connection management

I have an ASP.NET application that calls other web services through SSL (outside the application). I simply added a web reference (https://url/some.asmx) and used the web services and it works well. However, my questions are, how is the connection (channel) managed? is the connection to web services dropped after each web services call? or do they use the same connection (channel) for the subsequent calls? if they do, how long is the trusted connection kept alive?

Upvotes: 1

Views: 996

Answers (1)

3Dave
3Dave

Reputation: 29051

Classic ASMX web services maintain the connection for a single request - that's why the methods you call via the web service class must be static. A SOAP call is very similar to a plain vanilla HTTP Request:

  1. Open connection to URL
  2. Pass in request - get/post, etc
  3. Server renders an XML (SOAP) response
  4. Connection is closed
  5. Client processes response.

The web service framework wraps most of this so that you can conveniently access the web service as if it were a local object, but there is no server-side object instance persistence any more than there is for an ASPX page.

WCF services, on the other hand, maintain the connection until the proxy object is closed. This gives you a LOT of power, but, of course, with great power comes great responsibility.

update: link regarding ssl caching:

http://social.msdn.microsoft.com/forums/en-US/asmxandxml/thread/f86066e0-a24b-4d5e-873c-ed427d1faef7/

Upvotes: 1

Related Questions