Mercurial > pidgin

changeset 27784:b6a9e2079d50

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Use PURPLE_CONNECTION_ERROR_NETWORK_ERROR as the connection error reason, which will allow libpurple's auto-reconnect to handle the reconnection instead of forcing it in the prpl
author Stu Tomlinson <stu@nosnilmot.com>
date Sat, 01 Aug 2009 15:59:40 +0000
parents c499a1e8ceff
children 7a61ed46f632 b55e1786d131
files libpurple/protocols/yahoo/libymsg.c
diffstat 1 files changed, 1 insertions(+), 6 deletions(-) [+]
line wrap: on
line diff
--- a/libpurple/protocols/yahoo/libymsg.c	Sat Aug 01 15:32:38 2009 +0000
+++ b/libpurple/protocols/yahoo/libymsg.c	Sat Aug 01 15:59:40 2009 +0000
@@ -2035,7 +2035,6 @@
 	char *fullmsg;
 	PurpleAccount *account = gc->account;
 	PurpleConnectionError reason = PURPLE_CONNECTION_ERROR_OTHER_ERROR;
-	gboolean reconnect = FALSE;
 
 	while (l) {
 		struct yahoo_pair *pair = l->data;
@@ -2086,8 +2085,8 @@
 	case 52:
 		/* See #9660. As much as we know, reconnecting shouldn't hurt */
 		purple_debug_info("yahoo", "Got error 52, Set to autoreconnect\n");
-		reconnect = TRUE;
 		msg = g_strdup_printf(_("Unknown error"));
+		reason = PURPLE_CONNECTION_ERROR_NETWORK_ERROR;
 		break;
 	case 1013:
 		msg = g_strdup(_("Invalid username"));
@@ -2105,10 +2104,6 @@
 	purple_connection_error_reason(gc, reason, fullmsg);
 	g_free(msg);
 	g_free(fullmsg);
-
-	/* In case of error 52, we reconnect */
-	if(reconnect)
-		purple_account_connect(account);
 }
 
 static void yahoo_process_addbuddy(PurpleConnection *gc, struct yahoo_packet *pkt)