There was a circumstance where the framed input stream could hang if the 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.
There was a circumstance where the framed input stream could hang if the
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: a1a4b28b82a3276cc491891159dd9963a0a72fae@2693 542714f4-19e9-0310-aa3c-eee0fc999fb1

threerings/narya,threerings/narya,threerings/narya,threerings/narya,threerings/narya