diff libpurple/protocols/jabber/jabber.c @ 25189:05693f6885a4

Support old (XEP v1.3) Entity Capabilities alongside the new ones. The ext structures from v1.3 are stored in a ref-counted structure that is shared among all instances of the ClientInfo that share the same 'node' (unique per client). exts are only used for v1.3-entity capabilities clients and are not shared with caps that specify the 'hash' attribute (required in v1.5). The jabber_caps_cbplususerdata is also ref-counted and will never leak, even if some disco#info responses from a client return errors.

--- a/libpurple/protocols/jabber/jabber.c	Wed Dec 17 04:33:00 2008 +0000
+++ b/libpurple/protocols/jabber/jabber.c	Fri Dec 19 04:11:07 2008 +0000
@@ -2425,7 +2425,7 @@
 	}
 
 	/* Is this message sufficiently useful to not just fold it in with the tail error condition below? */
-	if(!jbr->caps) {
+	if(!jbr->caps.info) {
 		*error = g_strdup_printf(_("Unable to buzz, because there is nothing known about user %s."), username);
 		return FALSE;
 	}