[Standards-JIG] Re: Jabber external components: going out of style
stpeter at jabber.org
Tue May 30 16:16:49 UTC 2006
-----BEGIN PGP SIGNED MESSAGE-----
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'/>
> 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
> 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?
Jabber Software Foundation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
More information about the Standards