comparison libpurple/protocols/jabber/jabber.c @ 29288:4189f9e1627b

jabber: Pedantically this bothered me, but changing the message to definitively say which was going to happen next would duplicate logic from try_srv_connect().
author Paul Aurich <paul@darkrain42.org>
date Thu, 21 Jan 2010 20:28:41 +0000
parents ddad759dc05b
children 31d9677b0c36 9cdf9bc6c1ed
comparison
equal deleted inserted replaced
29287:ddad759dc05b 29288:4189f9e1627b
676 676
677 static void 677 static void
678 jabber_login_callback(gpointer data, gint source, const gchar *error) 678 jabber_login_callback(gpointer data, gint source, const gchar *error)
679 { 679 {
680 PurpleConnection *gc = data; 680 PurpleConnection *gc = data;
681 JabberStream *js = gc->proto_data; 681 JabberStream *js = purple_connection_get_protocol_data(gc);
682 682
683 if (source < 0) { 683 if (source < 0) {
684 if (js->srv_rec != NULL) { 684 if (js->srv_rec != NULL) {
685 purple_debug_error("jabber", "Unable to connect to server: %s. Trying next SRV record.\n", error); 685 purple_debug_error("jabber", "Unable to connect to server: %s. Trying next SRV record or connecting directly.\n", error);
686 try_srv_connect(js); 686 try_srv_connect(js);
687 } else { 687 } else {
688 purple_debug_info("jabber","Couldn't connect directly to %s. Trying to find alternative connection methods, like BOSH.\n", js->user->domain); 688 purple_debug_info("jabber","Couldn't connect directly to %s. Trying to find alternative connection methods, like BOSH.\n", js->user->domain);
689 js->srv_query_data = purple_txt_resolve("_xmppconnect", 689 js->srv_query_data = purple_txt_resolve("_xmppconnect",
690 js->user->domain, txt_resolved_cb, js); 690 js->user->domain, txt_resolved_cb, js);
691 } 691 }
692 return; 692 return;
693 } 693 }