If a connection is sitting in the system but is closed (perhaps possible
through some well-timed disconnection early in the initialization phase), we should consider it idle because then we'll catch it on the next tick and flush it whereas otherwise it would just sit around forever until someone logged in from that IP again. git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2788 542714f4-19e9-0310-aa3c-eee0fc999fb1
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
//
|
||||
// $Id: Connection.java,v 1.15 2002/12/22 19:13:38 mdb Exp $
|
||||
// $Id: Connection.java,v 1.16 2003/08/20 19:32:27 mdb Exp $
|
||||
|
||||
package com.threerings.presents.server.net;
|
||||
|
||||
@@ -272,7 +272,7 @@ public abstract class Connection implements NetEventHandler
|
||||
return false;
|
||||
}
|
||||
if (isClosed()) {
|
||||
return false;
|
||||
return true;
|
||||
}
|
||||
Log.info("Disconnecting non-communicative client [conn=" + this +
|
||||
", idle=" + idleMillis + "ms].");
|
||||
|
||||
Reference in New Issue
Block a user