View Issue Details

IDProjectCategoryView StatusLast Update
0000116JamochaMUDMain Programpublic2005-09-25 18:49
ReporterjeffnikAssigned Tojeffnik 
PrioritynormalSeverityminorReproducibilitysometimes
Status closedResolutionfixed 
Product Version1.2 rc1 
Target VersionFixed in Version1.2 rc1 
Summary0000116: JamochaMUD does not always indicate disconnection or lost connection
DescriptionJamochaMUD will not always indicate that it has been disconnected or has lost connection to a previously connected MU*. Often this disconnect is only displayed when the user tries to send a command to the MU* post-disconnection.
TagsNo tags attached.

Activities

jeffnik

2005-09-25 02:56

administrator   ~0000086

The try/catch method in MuSocket was moved outside of the "while" loop that read input from the MU*. This more accurately catches when a socket has been disconnected and then uses the catch method to update the disconnection notices for the user.

Issue History

Date Modified Username Field Change
2005-09-25 02:42 jeffnik New Issue
2005-09-25 02:56 jeffnik Status assigned => resolved
2005-09-25 02:56 jeffnik Fixed in Version => 1.2 rc1
2005-09-25 02:56 jeffnik Resolution open => fixed
2005-09-25 02:56 jeffnik Note Added: 0000086
2005-09-25 18:49 jeffnik Status resolved => closed