Note that there are some explanatory texts on larger screens.

plurals
  1. USSixto Saez
    primarykey
    data
    text
    plurals
    1. COSorry for the delay, I forgot about this answer. Service throttling could still come into play because of the different kinds of sessions that may be established in WCF. There are application (i.e. per session), transport, security, and reliable session types all of which count against the max sessions allowed setting. Closing the client could be completing the session termination process thus freeing up server side resources. The only "session-less" binding is basicHttp with no authentication configured. The other bindings use some sort of session to implement their capabilities.
      singulars
    2. COYou should reconsider wrapping your client object in "using". This post has a good explanation why you shouldn't: http://www.danrigsby.com/blog/index.php/2008/02/26/dont-wrap-wcf-service-hosts-or-clients-in-a-using-statement/
      singulars
    3. COSomething doesn't seem correct about the situation you are describing. Calling a service with values (username, password, ...) in the query string seems to fit a REST-based service. You say the service you are calling is providing WSDL so it seems to be a soap-based service. You can't have both calling schemes because a soap service will only have access to anything in the soap envelope and ignore the query string values. Could you clarify whether this is actually a soap-based service? Thanks!
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload