milliseconds. I want to know what in the fuck those were.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2840 542714f4-19e9-0310-aa3c-eee0fc999fb1
services that registered (ignoring unregisters) but I can't get it to
cough up the problem on my machine, so it's a little hard to test. If you
fine cvs readers want to take a peek that would be great. Hurray for
debug code.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2836 542714f4-19e9-0310-aa3c-eee0fc999fb1
post events to an object that is already destroyed, we'll allow
transactions to be started on non-active objects and we'll just log a
warning when the transaction is finally committed like we do for all other
events on non-active objects.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2835 542714f4-19e9-0310-aa3c-eee0fc999fb1
space, it ends up considering up to 10,000 nodes with a max path length of
50 which causes the client to hang for like 5 seconds. Not so good. With a
max path length of 20, that comes down to about 1,300 nodes which ends up
being non-linearly faster.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2825 542714f4-19e9-0310-aa3c-eee0fc999fb1
client is disconnected, unsubscribe immediately. We normally unsubscribe
when the client loses its connection but it's possible for a subscription
request to come in and the client to lose connection before we can
communicate the object available response.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2824 542714f4-19e9-0310-aa3c-eee0fc999fb1
erroneously decide that we have stale subscriptions around, and log stale
subscriptions if we do end up clearing them.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2817 542714f4-19e9-0310-aa3c-eee0fc999fb1
pirate selection and the time we manage to load up their pirate.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2816 542714f4-19e9-0310-aa3c-eee0fc999fb1
creates an Object[] as well. Now we cache the Field instances and look
them up ourselves which will likely be much more efficient at only a small
additional memory cost.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2805 542714f4-19e9-0310-aa3c-eee0fc999fb1
server and added more sanity checking to handleJoinCluster().
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2801 542714f4-19e9-0310-aa3c-eee0fc999fb1
what we said to the teller so that we remember that we have the
auto-response active.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2798 542714f4-19e9-0310-aa3c-eee0fc999fb1
method of the chat director prior to sending cluster chat.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2796 542714f4-19e9-0310-aa3c-eee0fc999fb1
by returning null instead of a filtered version.
- Changed the MuteDirector to implement ChatFilter.
- ChatDirector no longer needs a reference to the MuteDirector because
the outgoing mute-checking is now handled by the standard filtering code.
- Fixed a bug introduced by Walter back in December that caused the
MuteDirector to be _removed_ as a validator the first time you try to
/tell to a player that you've muted. How we never detected this, I'll
stay awake at night wondering...
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2795 542714f4-19e9-0310-aa3c-eee0fc999fb1
every time a particular person hears another person say something.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2794 542714f4-19e9-0310-aa3c-eee0fc999fb1
Michael Bayne