030545b8ebb7a746629f80548cbf7b7f97c36931
in the low-level invocation services whereby after a disconnect, any InvocationReceiver registration would be wholly ignored due to the previous registrations being left in the receivers set and DSet refusing to add duplicate instances of the registration. This wasn't immediately apparent because the initial set of registrations always happens in the same order and thus are equally useful after the reconnect and any other registrations are removed during the normal course of affairs. But if a user disconnects *during* a puzzle, they will leave that puzzle's registration around and be unable to play that (or any) puzzle again until they log off and back on. git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2707 542714f4-19e9-0310-aa3c-eee0fc999fb1
Description
Distributed application framework, good for MMOGs
Languages
Java
69.1%
ActionScript
26.6%
C++
3.1%
Go Template
0.8%
HTML
0.2%
Other
0.1%