circumstances where they aren't around when they should be.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2702 542714f4-19e9-0310-aa3c-eee0fc999fb1
- Require a Comparable key in get() and containsKey().
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2698 542714f4-19e9-0310-aa3c-eee0fc999fb1
allowing things to get out of hand. Since getOccupantInfo may normally
return null, doing so in our strange failure case will not cause further
freakout.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2697 542714f4-19e9-0310-aa3c-eee0fc999fb1
code did that due to eventuall getting out of the loop, the "fixed" code
failed to do it if we failed to fill our buffer up on the first read.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2695 542714f4-19e9-0310-aa3c-eee0fc999fb1
the loop, so I'm rolling back to the previous version since I can't even
log in to my server with this change. Mike if you want to take a look or
tell me what jimmyjamming needs to be done to make this change work, that
would be great.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2694 542714f4-19e9-0310-aa3c-eee0fc999fb1
frame size was exactly the same size as the buffer and no future messages
came down the pipe to wake us up again. This probably would have had to
happen very early in the session as the buffer gets bigger and bigger to
accomodate the largest frame seen during the entire session and
asynchronous messages are coming in more frequently as well. Thus it's
extremely unlikely that this ever actually hung. In any case, we now log
that circumstance (and do the right thing) so we can see if the log
message turns up in future bug reports.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2693 542714f4-19e9-0310-aa3c-eee0fc999fb1
catastrophic fuckola, but we can wait until later to freak out.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2690 542714f4-19e9-0310-aa3c-eee0fc999fb1
hotspot, which does not need to be the upper left coordinate. So we let
the sprite do the right thing and we just center on the hotspot.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2681 542714f4-19e9-0310-aa3c-eee0fc999fb1
beginning. To do this more efficiently, we end up having to do some
jockeying.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2679 542714f4-19e9-0310-aa3c-eee0fc999fb1
going to need to make this customizable by derived classes at some point.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2670 542714f4-19e9-0310-aa3c-eee0fc999fb1
fly in the future; it also now provides efficient tileset name to tileset
id mappings which is exported via the TileSetRepository interface. Lastly,
TileManager now relies on TileSetRepository to efficiently provide tiles
by name or id and no longer maintains its own cache (because the
BundledTileSetRepository already maintains the same mappings).
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2663 542714f4-19e9-0310-aa3c-eee0fc999fb1
said; prune any big history when a new message is noted.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2657 542714f4-19e9-0310-aa3c-eee0fc999fb1
the only circumstance where we're not getting sent our own message back to
us.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2654 542714f4-19e9-0310-aa3c-eee0fc999fb1
every type of chat object known to man capable of reporting who's
listening.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2653 542714f4-19e9-0310-aa3c-eee0fc999fb1
Michael Bayne