Google Talk typing notification

2 maj 2007 kl. 08.01 skrev Matt Herron:

Hi Matt,

In order to receive typing notifications through XMPP you
need to do  
one of two things (the latter preferred).

1) Send a message first with the <composing/> child.
So for example  
if I write to you I add the
    <composing/> child to my message which notifies
the other end  
that I'm interested in getting
    composing events back.

2) Implement XEP-0085, http://w
ww.xmpp.org/extensions/xep-0085.html
    This is the XMPP Extension Proposal to add support for
typing  
notifications and I guess this is
    what they are using at Google (haven't confirmed yet).
As said  
this is the preferred way.

Best Regards,
   Mikael Hallendal

> Hi
>
> I seem to not be able to catch typing notifications
from google  
> talk accounts. I look for messages with type chat and
has a  
> composing child node. Is there something special I have
to do with  
> loudmouth or is this a problem with google talk's
protocol?
>
> Thanks
>        Matt
> _______________________________________________
> Loudmouth mailing list
> Loudmouthlists.imendio.com
> h
ttp://lists.imendio.com/mailman/listinfo/loudmouth


--
Imendio AB, http://www.imendio.com


_______________________________________________
Loudmouth mailing list
Loudmouthlists.imendio.com
h
ttp://lists.imendio.com/mailman/listinfo/loudmouth

Currently, when Loudmouth receives a message that has an ID,
it looks up the
ID in LmConnection->id_handlers. It does this regardless
of the message type:
the handler will get called even if the message is an e.g.
<iq type="get">.

Patch attached; also available from git here:

h
ttp://projects.collabora.co.uk/~daf/loudmouth.git/

-- 
Dafydd

_______________________________________________
Loudmouth mailing list
Loudmouthlists.imendio.com
h
ttp://lists.imendio.com/mailman/listinfo/loudmouth

29 maj 2007 kl. 15.46 skrev Dafydd Harries:

Hi,

I've added this to the issue tracker as LM-106 [1].

Thanks,
   Mikael Hallendal

[1] htt
p://developer.imendio.com/issues/browse/LM-106

>
> Currently, when Loudmouth receives a message that has
an ID, it  
> looks up the
> ID in LmConnection->id_handlers. It does this
regardless of the  
> message type:
> the handler will get called even if the message is an
e.g. <iq  
> type="get">.
>
> Patch attached; also available from git here:
>
> h
ttp://projects.collabora.co.uk/~daf/loudmouth.git/
>
> -- 
> Dafydd
> <lm-reply-handlers.diff>
> _______________________________________________
> Loudmouth mailing list
> Loudmouthlists.imendio.com
> h
ttp://lists.imendio.com/mailman/listinfo/loudmouth


--
Imendio AB, http://www.imendio.com


_______________________________________________
Loudmouth mailing list
Loudmouthlists.imendio.com
h
ttp://lists.imendio.com/mailman/listinfo/loudmouth

Ar 11/06/2007 am 14:48, ysgrifennodd Mikael Hallendal:
> 29 maj 2007 kl. 15.46 skrev Dafydd Harries:
> 
> Hi,
> 
> I've added this to the issue tracker as LM-106 [1].
> 
> Thanks,
>   Mikael Hallendal
> 
> [1] htt
p://developer.imendio.com/issues/browse/LM-106
> 
> >
> >Currently, when Loudmouth receives a message that
has an ID, it  
> >looks up the
> >ID in LmConnection->id_handlers. It does this
regardless of the  
> >message type:
> >the handler will get called even if the message is
an e.g. <iq  
> >type="get">.
> >
> >Patch attached; also available from git here:
> >
> >h
ttp://projects.collabora.co.uk/~daf/loudmouth.git/

Thinking about it, this patch is inadequate.

If you only check the ID, then you are susceptible to
spoofing attacks. The
code should also check that the result/error message was
sent by the JID that
the get/set was sent to.

My understanding is that messages with no to address should
receive replies
with no from address, or perhaps with a from address that's
the server we're
connected to.

-- 
Dafydd
_______________________________________________
Loudmouth mailing list
Loudmouthlists.imendio.com
h
ttp://lists.imendio.com/mailman/listinfo/loudmouth