>From my experience, the problem has to do with more than just number of connections. I've reached the limit from spawning too many processes.<br><br>
<div><span class="gmail_quote">On 6/28/05, <b class="gmail_sendername">Jp Calderone</b> <<a href="mailto:exarkun@divmod.com">exarkun@divmod.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Tue, 28 Jun 2005 10:47:04 +0100, Toby Dickenson <<a href="mailto:tdickenson@devmail.geminidataloggers.co.uk">
tdickenson@devmail.geminidataloggers.co.uk</a>> wrote:<br>>Im finding that Win32Reactor raises an exception on every iteration of the<br>>main loop if I exceed the limit of 64 WaitForMultipleObjects.<br>><br>>I would prefer to avoid this fairly obvious denial-of-service problem by
<br>>limiting the number of concurrent client connections. Is there a standard<br>>solution for this?<br>><br><br>Count the number of connections you have accepted. When you get up to 62 or 63 or so, stop accepting new ones. If
ServerFactory.buildProtocol() returns None, Twisted immediately closes the accepted connection. If you do this (perhaps in conjunction with calling stopListening() on the port returned by listenXYZ()), you'll never overrun the 64 object limit.
<br><br>Jp<br><br>_______________________________________________<br>Twisted-Python mailing list<br><a href="mailto:Twisted-Python@twistedmatrix.com">Twisted-Python@twistedmatrix.com</a><br><a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python">
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br></blockquote></div><br>