changeset 8383:ae15e717ca75

[gaim-migrate @ 9111] (00:18:52) lschiere: marv: https://sourceforge.net/tracker/?func=detail&atid=300235&aid=908071&group_id=235 (00:21:24) marv: what does gc->wants_to_die = TRUE; do? is that some sort of hint for the autoreconnect plugin? (00:21:43) lschiere: kinda sorta (00:21:51) lschiere: if a gc wants to die, you signed off (00:22:01) lschiere: if it doesn't, then something killed it, and it should be reconnected (00:22:41) lschiere: i'm not sure how we used to handle that kind of thing for aim (00:23:03) lschiere: but basically if that's what he's doing, he's mimicing you signing off manually (00:23:52) marv: yeah, all the patch does is add that line right before the gaim_connection_error when yahoo receives a patch telling us we got signed off because we signed on with another client (00:24:22) lschiere: i dare say it would work, as long as we can uniquely id when we are kicked off for that reason (00:25:07) marv: i think we do a pretty good job of that, i haven't heard any reports of anyone getting that message when that's not what happened. (00:25:22) marv: then again, i don't remember when i added that, and if yahoo's worked since then. (00:25:36) lschiere: *nods* basically, Rob Foehl figured out a predictable way to work around yahoo being too dumb to handle 2 instances of the same sn on at once. Jabber's done that for years, and aim even figured it out, so you'd think yahoo would get a clue... ;-) committer: Tailor Script <[e-mail]>

--- a/src/protocols/yahoo/yahoo.c	Tue Mar 02 05:14:18 2004 +0000
+++ b/src/protocols/yahoo/yahoo.c	Tue Mar 02 05:19:53 2004 +0000
@@ -304,6 +304,7 @@
 	char *name = NULL;
 
 	if (pkt->service == YAHOO_SERVICE_LOGOFF && pkt->status == -1) {
+		gc->wants_to_die = TRUE;
 		gaim_connection_error(gc, _("You have been logged off as you have logged in on a different machine or device."));
 		return;
 	}