[Standards-JIG] Re: Jabber external components: going out of style

Peter Saint-Andre stpeter at jabber.org
Tue May 30 16:16:49 UTC 2006

Hash: SHA1

Gaston Dombiak wrote:
> Hey Peter,
>> Presumably an external component that connects via JEP-0114 could
>> request the roster for any user on the server, no? And it could even
>> send presence for any user (probably with negative priority) and then
>> receive roster updates.
> In our implementation packets sent by external components to the server will 
> be routed by the server no matter the FROM and TO attributes values. 
> However, if the external component sends this packet:
> <iq from='juliet at example.com/balcony' type='get' id='roster_1'>
>   <query xmlns='jabber:iq:roster'/>
> </iq>
> then the server will route it to the roster handler and will end up 
> returning the roster to the user juliet that logged from the balcony. 

Right. Or it will result in an internal error if there is no such
resource. Hmm.

> So I'm wondering how should external components request a user's roster and 
> indicate the server that the answer should be sent to the component and not 
> the user? Is there any JEP that covers this scenario?

Not yet.


- --
Peter Saint-Andre
Jabber Software Foundation

Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060530/2ff93c6a/attachment.bin>

More information about the Standards mailing list