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 _______________________________________________ libsecondlife-dev mailing list [email protected] https://mail.gna.org/listinfo/libsecondlife-dev
