<connectionManagement>
<add address="*" maxconnection="Number of concurrent connections"/>
</connectionManagement>
Yuri Misnik
-----Original Message-----
From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On
Behalf Of FRIEDMAN,Adam
Sent: Wednesday, June 11, 2003 1:24 PM
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] WebService Proxy
Check out the MSDN docs for the following index keywords.
For web.config:
- <connectionManagement> element
For programmatic adjustment:
- ServicePointManager.FindServicePoint method
- ServicePoint.ConnectionLimit property
-----Original Message-----
From: Leonel Waisblatt [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 11, 2003 1:59 AM
To: [EMAIL PROTECTED]
Subject: [ADVANCED-DOTNET] WebService Proxy
Hi,
im having the this problem:
I have an aspx page that connects to a webservice trough a SoapHttpClientProtocol
proxy.
while a stress test I realize that a lot of requests to the webservice returns
timeout. I'm thinking that this problem is because http 1.1 protocol, that only
supports 2 connections at the same time, so a big percentage of the requests are
queued, and finally returns by timeout. As i read on msdn winhttp protocol doesn�t
have this restriction, thus Im traying to make the webservice's requests via WinHttp,
but I can�t.
Any Clue??
Thnks in advance, bye...
Leonel.
Notice:
The information contained in this e-mail message and any attached files may
be confidential information, and may also be the subject of legal
professional privilege. If you are not the intended recipient any use,
disclosure or copying of this e-mail is unauthorised. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete all copies of this transmission together with any attachments.
