Client will not disconnect quickly if the connection is lost

Since Natty (AFAIK) when the connection is lost, Twisted takes too long to notice.

For example, consider the following situation: you sleep your computer, and wake it up one hour again... the server already closed the connection for your client (it has its own timeout), and the client tries to do a Ping to the server, or do any operation, but the connection is down.

Previously, Twisted will raise connectionLost on the first usage in this case, but now it does it after 30 minutes.

So, the client needs to implement its own timeout, and raise connectionLost if the "ping" is not answered in 3 minutes.