Michael Bayne 6bf19ba419 We need to tell the clients that we did logoff after we've actually shutdown ...

and clear out our socket. The DID_LOGOFF notification is sent out to the client
after we've sent our LOGOFF request to the server, so we need to be sure that
no other messages go to the server after the LOGOFF request otherwise we risk
the server generating spurious warnings (like it does currently in the
thousands daily).


git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@5297 542714f4-19e9-0310-aa3c-eee0fc999fb1

2008-08-07 20:58:16 +00:00

..

as/com/threerings

We need to tell the clients that we did logoff after we've actually shutdown

2008-08-07 20:58:16 +00:00

java/com/threerings

It's not entirely obvious how we should respond to multiple calls to logoff()

2008-08-07 16:52:19 +00:00

player/com/threerings/util/env

Stop switching different source files into Environment.as's place. Instead build tiny swc's with the player-specific Environment.as and the thane-specific one. Then compile naryalib.swc with one of these tiny swc's as an external library. When we compile the final executables we'll do a inclusive linking to get the right implementation into place.

2008-06-13 03:39:26 +00:00

thane/com/threerings/util/env

Stop switching different source files into Environment.as's place. Instead build tiny swc's with the player-specific Environment.as and the thane-specific one. Then compile naryalib.swc with one of these tiny swc's as an external library. When we compile the final executables we'll do a inclusive linking to get the right implementation into place.

2008-06-13 03:39:26 +00:00