they leave our scene. Somehow we're not properly catching cluster
departures in some circumstances.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2789 542714f4-19e9-0310-aa3c-eee0fc999fb1
through some well-timed disconnection early in the initialization phase),
we should consider it idle because then we'll catch it on the next tick
and flush it whereas otherwise it would just sit around forever until
someone logged in from that IP again.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2788 542714f4-19e9-0310-aa3c-eee0fc999fb1
and refuse subscriptions to invalid oids (it's not out of the realm of
possibility that the clients were somehow subscribing to oid 0 and funny
things were happening).
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2778 542714f4-19e9-0310-aa3c-eee0fc999fb1
never started and the server eventually gave me the boot."
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2776 542714f4-19e9-0310-aa3c-eee0fc999fb1
programmatically or it will be assumed to be the same as the normal
resource URL.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2774 542714f4-19e9-0310-aa3c-eee0fc999fb1
by making these transient we can hopefully debug it more effectively if it
happens in the future.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2773 542714f4-19e9-0310-aa3c-eee0fc999fb1
the reporting interval. Now we can see if we're leaking intervals (which
would be double plus ungood).
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2769 542714f4-19e9-0310-aa3c-eee0fc999fb1
because odd things frequently happen if a player somehow double clicks or
in some other way queues up a change scene then a change loc from the
previous scene.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2768 542714f4-19e9-0310-aa3c-eee0fc999fb1
around in there for other reasons. We also avoid looking up the entry in
the jar file every time it is requested.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2766 542714f4-19e9-0310-aa3c-eee0fc999fb1
successfully unpacked its jar file so that we can report bundle download
borkage and retry in the face of potentially transient fuckolas.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2764 542714f4-19e9-0310-aa3c-eee0fc999fb1
problem with not being able to rename some, but not all, of the old jar
files prior to patching them.
Also, took out the assume v0.22 hack as we should be good to go on that
front by the next release, the stragglers will just have to download a
full update (which is safer anyway).
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2754 542714f4-19e9-0310-aa3c-eee0fc999fb1
frame tick interval 10ms on Windows because any non-multiple of 10 causes
the big fat fuckola in the form of heinously accelerated clock drift.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2751 542714f4-19e9-0310-aa3c-eee0fc999fb1
seconds to pass in between ping/pong latency samples. Additionally, we
resync the clock every 10 minutes.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2748 542714f4-19e9-0310-aa3c-eee0fc999fb1
and dobj thread until they're both empty (or it has been passed 50 times)
and then shuts the threads down.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2744 542714f4-19e9-0310-aa3c-eee0fc999fb1
the JNLP versioned resource protocol so that it can download jardiffs
instead of whole new jar files when a resource bundle is updated.
Unversioned http downloads (which we'll probably continue to use for the
dynamically generated island bundles) are currently not working.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2739 542714f4-19e9-0310-aa3c-eee0fc999fb1
Michael Bayne