If you want to programmatically control it, Do the following: ServicePointManager.DefaultConnectionLimit = 20; // increase from default 2 to 20 concurrent to the same site without following the Http Spec.
Regards, Hun Boon Teo http://www.geocities.com/teohunboon ----- Original Message ----- From: "TIAGO PASCOAL (Interaction)" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 02, 2002 10:36 PM Subject: Re: [ADVANCED-DOTNET] Threading is blocking itself or ? Put something like this in machine.config or web.config <System.Net> <ConnectionManagement> <add address="*" maxconnection="XXX" /> </ConnectionManagement> </System.Net> Not sure if the elements and attribute names are totally correct since i'm working by memory. But it's something like this. -----Original Message----- From: Ed Stegman [mailto:[EMAIL PROTECTED]] Sent: sábado, 31 de Agosto de 2002 9:02 To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Threading is blocking itself or ? Is there a work around for this wrt .NET HttpWebRequest/Response objects? I have some associates that have spent months putting together what they thought was a high throughput B2B component and they are totally toast because of this behavior. They are conversing with a dedicated HTTPS server farm, and need to be making a much larger number of concurrent connections than the 2 they are getting. Spinning off a new AppDomain has no effect. Spinning off a new process does, but at only 2 connections per process, it's not a feasible solution. Keep Smilin' Ed Stegman -----Original Message----- From: Greg Reinacker I'm not sure about the SOAP toolkit you're using, but many toolkits (.NET included) will, by default, limit the number of concurrent HTTP connections to a single endpoint to 2 (this is part of the HTTP 1.1 spec, I believe). So you may be seeing an artificial bottleneck, where all of your requests are being funneled through 2 connections. snip... Greg Reinacker Reinacker & Associates, Inc. http://www.rassoc.com http://www.rassoc.com/gregr/weblog/ You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
