That sounds like a good plan. This probably will not catch server crashes, however, as no KickUser packet would be sent. As UDP is connectionless, the only way to detect such a crash is to issue a ping style packet every so often, or listen for such ping packets if the server already sends them. Do we have any information on the method the official client uses to detect a sudden server disconnection?
-Sam -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Hurliman Sent: Friday, July 14, 2006 1:00 PM To: Development list for libsecondlife Subject: Re: [libsecondlife-dev] KickUser and other disconnection handling [EMAIL PROTECTED] wrote: > After being idle for a few hours (somewhere between 4 and 5 perhaps) > libsecondlife received an unsolicited event in the form of a KickUser packet > (reported erroneously as a duplicate packet). This, and all other events > that would indicate a disconnection, should be handled in libsecondlife by > reporting the loss of connection via a callback and allowing a reconnection > by the application if desired. > > Information on such disconnections would be useful to the application, so I > would suggest not handling it completely behind the scenes with an automatic > reconnection. Reporting with a callback and making sure the library is in a > state where it can cleanly connect again through the normal login process > are the important things. > > Thoughts? > > -Sam > I was just talking about this yesterday. The idea was to automatically disconnect everything internally and reset state, then fire a DisconnectEvent if there's a registered client handler. John _______________________________________________ libsecondlife-dev mailing list [email protected] https://mail.gna.org/listinfo/libsecondlife-dev _______________________________________________ libsecondlife-dev mailing list [email protected] https://mail.gna.org/listinfo/libsecondlife-dev
