MaxConnectionsPerServer
- From: Laurent Bugnion <galasoft-lb@xxxxxxxxxx>
- Date: Thu, 10 Aug 2006 14:15:02 +0200
Hi,
In Windows (XP and possibly other versions too), there is a registry key named "MaxConnectionsPerServer" allowing you to specify how many concurrent connections per client to a server are allowed. The default is 2.
This means that I can only have two parallel connections to a server inside a browser window, or from multiple browser windows if they run in the same IE instance (same process).
We are currently investigating the use of web services to keep a connection to the server open, in order to react more quickly to incoming alarms. In our scenario, we would send a web service request, and then wait on the server until an alarm comes in, or until the timeout comes. Immediately after the response arrives on the client, we would send the next request.
However, we are confronted with the limitation described above. This limit can be changed in the registry (up to 24), but it's not a viable solution in the web case (you may not modify the client's registry).
My questions:
- Is that limit really the big issue that we foresee in the case of web services?
- Is there a workaround?
- If we manage to change it on the client, what is the risk by setting this value to the maximum? (24)
- Did we miss something?
Thanks,
Laurent
--
Laurent Bugnion, GalaSoft
Software engineering: http://www.galasoft-LB.ch
Private/Malaysia: http://mypage.bluewin.ch/lbugnion
Support children in Calcutta: http://www.calcutta-espoir.ch
.
- Prev by Date: Re: Inherited web.config ASP.NET 2.0
- Next by Date: User control in PlaceHolder, in a MasterPage
- Previous by thread: IIS 6.0 Seperate Pools! How to go about doing it in Windows XP?
- Next by thread: User control in PlaceHolder, in a MasterPage
- Index(es):
Relevant Pages
|
