Changeset 0c78bb7 for protocols/jabber

Timestamp:

2015-10-21T06:05:17Z (9 years ago)

Author:

dequis <dx@…>

Branches:

master

Children:

5307e88

Parents:

e4145d9

Message:

jabber: Fix outgoing google talk typing notifications

Since bare JIDs from typing notifications are now accepted, the other
buddy objects never get the flag JBFLAG_DOES_XEP85 set. This fixes it by
checking both the buddy with resource and the bare one, with the
implication that if the bare JID has that flag, all other resources get
typing notifications.

Follow up to the previous commit, splitting since they are actually
unrelated fixes, although this one is a consequence of the previous one.

File:

• protocols/jabber/jabber.c (modified) (2 diffs)

protocols/jabber/jabber.c

@@ -592 +592 @@
 {
         struct jabber_data *jd = ic->proto_data;
-        struct jabber_buddy *bud;
+        struct jabber_buddy *bud, *bare;
 
         /* Enable typing notification related code from now. */
         jd->flags |= JFLAG_WANT_TYPING;
 
-        if ((bud = jabber_buddy_by_jid(ic, who, 0)) == NULL) {
+        if ((bud = jabber_buddy_by_jid(ic, who, 0)) == NULL ||
+            (bare = jabber_buddy_by_jid(ic, who, GET_BUDDY_BARE)) == NULL) {
                 /* Sending typing notifications to unknown buddies is
                    unsupported for now. Shouldn't be a problem, I think. */
@@ -603 +604 @@
         }
 
-        if (bud->flags & JBFLAG_DOES_XEP85) {
+
+        if (bud->flags & JBFLAG_DOES_XEP85 || bare->flags & JBFLAG_DOES_XEP85) {
                 /* We're only allowed to send this stuff if we know the other
-                   side supports it. */
+                   side supports it. If the bare JID has the flag, all other
+                   resources get it, too (That is the case in gtalk) */
 
                 struct xt_node *node;