Hello Garyc,<div><br></div><div>This is not twisted's fault. Pulling a network plug doesn't tell the server that the client went away immediately since the connection wasn't closed properly. Pulling the plug produces TCP half-open scenario when one thinks that the connection is still up. This can be remedied by polling/hearbeat/keepalive logic. You can make your twisted server aware of the keepalive timeouts by turning on setTcpKeepAlive to 1:</div>
<div><br></div><div>self.transport.setTcpKeepAlive(1)</div><div><br></div><div>Cheers,</div><div>Alvin</div><div><br><br><div class="gmail_quote">On Wed, Feb 17, 2010 at 12:15 AM, gary clark <span dir="ltr"><<a href="mailto:burslem2001@yahoo.com">burslem2001@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello,<br>
<br>
I'm tested my client server model. The server being a twisted server.<br>
I am using the class NetstringReceiver. When I close down the client the appropriate call to close the connection is made "connectionLost". However when I just pull the client connection cable from the network. I would expect the call to be made to indicate a connection is lost at the twisted server. I dont see this.<br>
<br>
I am going through a local hub and not sure what at the moment to think of this. I am using ssl to communicate.<br>
<br>
If somebody could shed some light on this that would be great.<br>
<br>
Thanks,<br>
Garyc<br>
<br>
<br>
<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" target="_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><a href="http://www.alvinatorsplayground.blogspot.com/">http://www.alvinatorsplayground.blogspot.com/</a><br>
</div>