actually disconnecting (due to EC2 woes, e.g.), let's try shutting down peers
if they haven't checked in for a while.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6636 542714f4-19e9-0310-aa3c-eee0fc999fb1
a non-weird function that just returns a useful value), and comment the
weirding (in this case, only in CustomClassStreamer.{read|write}Object, since
that's the only place where a race condition may occur.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6634 542714f4-19e9-0310-aa3c-eee0fc999fb1
our no synchronization at the cost of possibly doing some trivial extra work.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6633 542714f4-19e9-0310-aa3c-eee0fc999fb1
processing messages, so let's put a (logging) NOOP handler in place when we
disconnect it from the PresentsSession.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6629 542714f4-19e9-0310-aa3c-eee0fc999fb1
it seems like we're still getting messages from old connections.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6627 542714f4-19e9-0310-aa3c-eee0fc999fb1
differently (specifically, we want to enable SO_REUSEADDR in Spiral Knights).
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6625 542714f4-19e9-0310-aa3c-eee0fc999fb1
add(index,observer) used to return void and now it returns boolean. Really I'd
rather add(index,observer) and add(observer) both returned void and threw an
exception if a duplicate was detected (because wtf are you doing?), but
Collection dictates a signature of boolean add (elem) and if I changed that,
then *everybody* would need to recompile. Sigh. We'll just suck it up and leave
add(i,o) consistent with add(o) and have Narya rebuild agains the latest
bytecode.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6624 542714f4-19e9-0310-aa3c-eee0fc999fb1
lying around when the client reconnects. Let's try just clearing them out
again on resumption.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6619 542714f4-19e9-0310-aa3c-eee0fc999fb1
datagram PINGs. Let's make sure that the connection to which we're sending
the pong is the same one from which we received the ping. Ping, pong, ping,
pong.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6618 542714f4-19e9-0310-aa3c-eee0fc999fb1
us with lots of "Requested to clear unknown proxy" warnings in Spiral
Knights.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6606 542714f4-19e9-0310-aa3c-eee0fc999fb1
subclasses start nuking things, but once it is known that it will end.
It always bugged me in msoy that the session subclass has to do this (poorly). Seems patently
observer-ish. This fix has almost no runtime overhead and is backwards compatible. The name
isn't great, but I was leaving room for more methods in there should someone else find it
useful, such as sessionWillStart or even clientObject[Will|Did]Release.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6603 542714f4-19e9-0310-aa3c-eee0fc999fb1
go along with the public release I just did to Maven Central of the main jar
artifact.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6597 542714f4-19e9-0310-aa3c-eee0fc999fb1
constructors. Fixed ElementUpdatedEvent along the way.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6590 542714f4-19e9-0310-aa3c-eee0fc999fb1
Bruno Garcia