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
it's totally wacky to have the ctor you shouldn't use, be public, and the one
you should, not.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6588 542714f4-19e9-0310-aa3c-eee0fc999fb1
because that will overwrite the hackery we do with _oldEntry. Oh hackery, how
we love you so.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6586 542714f4-19e9-0310-aa3c-eee0fc999fb1
breaks streaming. Everyone will have to regenerate their services. Sorry! If
only I hadn't hardcoded the insertion of the constructor in the first place,
this would have all been nicely behind an abstraction boundary. It will be once
the services are regenerated.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6584 542714f4-19e9-0310-aa3c-eee0fc999fb1
streamed property of the event. It turns out to be cleaner to just set it in
the places where we know that we want a specific transport anyway.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6581 542714f4-19e9-0310-aa3c-eee0fc999fb1
Andrzej Kapolka