<< Duff’s Device | Home | Compound Keys: The Ally Of Evil >>

HTTP Connection Limits

Gavin blogs about how to circumvent the two connection limit in IE. RFC 2068 mandates this limit in the HTTP 1.1 specification.

If you are calling web services in .NET, or using the WebRequest or WebClient classes, you'll also run into this connection limit, which can really throttle applications using an application server through web services. Fortunately, you change the connection limit in a config file:

<connectionManagement>
    <add address="*" maxconnection="2">
    <add address="65.53.32.230" maxconnection="12">
</connectionManagement>

For more information, see one of the following:

PRB: Contention, Poor Performance, and Deadlocks When You Make Web Service Requests from ASP.NET Applications

At Your Service: Performance Considerations for Making Web Service Calls from ASPX Pages

Print | posted @ Wednesday, June 09, 2004 6:59 AM

Comments on this entry:

Gravatar # re: HTTP Connection Limits
by sanjeev batta at 11/10/2004 12:04 PM
Does this also apply to the remoting type calls to another machine.
  
Gravatar # re: HTTP Connection Limits
by Scott Allen at 11/10/2004 4:28 PM
Sanjeev: Yes, if you are using an HTTP channel. See &quot;Configuring the http channel&quot; in the following document: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/remotingconfig.asp
  
Comments have been closed on this topic.
Scott Allen
Posts - 869
Comments - 4493
Stories - 14