[Standards-JIG] Re: Whose avatar?

Heiner Wolf wolf at bluehands.de
Tue May 24 17:13:11 UTC 2005


I would like to repeat my proposal to add an application defined context to notifications. The client would supply an XML fragment with the subscription. The fragment will be included in notifications. The fragment would be transparent to the pubsub service. 

We can then standardize the format of this application context. I would defer this and let applications just use it until we have at lease a bit of experience. Remember: too many specs, not enough code. 

Each callback needs a user context. A subscription is a callback interface.

Sample subscription:
      <iq type='set'
          from='romeo at montague.net/orchard'
        <pubsub xmlns='http://jabber.org/protocol/pubsub'>
              node='avatar/info/juliet at capulet.com'
              jid='romeo at montague.net' >
--->        <context>Here could be the JID</context>

Sample pubsub#event:
      <message to="romeo at montague.net" from="pubsub.shakespeare.lit">
        <x xmlns="http://jabber.org/protocol/pubsub#event">
          <items node="avatar/info/juliet at capulet.com">
            <item id="current">
                node='avatar/data/juliet at capulet.com'
                id='109f4b3c50d7b0df729d299bc6f8e9ef9066971f' />
--->      <context>Here could be the JID</context>

Dr. Klaus H. Wolf
bluehands GmbH & Co.mmunication KG
+49 (0721) 16108 75
Jabber enabled Virtual Presence on the Web: http://www.lluna.de/
Open Source Future History: http://www.galactic-developments.com/

>-----Original Message-----
>From: standards-jig-bounces at jabber.org
>[mailto:standards-jig-bounces at jabber.org]On Behalf Of Tijl Houtbeckers
>Sent: Tuesday, May 24, 2005 7:00 PM
>To: Jabber protocol discussion list
>Subject: Re: [Standards-JIG] Re: Whose avatar?
>On Sun, 22 May 2005 20:57:13 +0200, Magnus Henoch <mange at freemail.hu>  
>> Magnus Henoch <mange at freemail.hu> writes:
>>> I could keep the mapping between JIDs and avatar pubsub nodes in
>>> private XML storage, updating it as I subscribe to new avatars.
>> I found some more time to hack avatars, which has led me to think
>> about this approach again.  I imagine something like the following:
>> <iq type='set'>
>>   <query xmlns='jabber:iq:private'>
>>     <mappings xmlns='http://jabber.org/protocol/pubsub-mapping'>
>>       <mapping user='juliet at capulet.com'
>> 	       jid='pubsub.capulet.com'
>> 	       node='juliet/geoloc'
>> 	       targetns='http://jabber.org/protocol/geoloc'/>
>>     </mappings>
>>   </query>
>> </iq>
>> with any number of <mapping/> nodes under <mappings/>.  It's
>> inconvenient that you can't use a delta to update this, but at least
>> it gets the work done without changes to server implementations.
>> This would be common to all clients that use data received from
>> pubsub.  What do you think about it?
>This would lead to sending (potentially) huge XML fragments to 
>the server,  
>for just adding 1 new person with an avatar or a "current song 
>etc. feature. However it's the only thing so far to provide 
>secure pubsub  
>events shared across multiple clients. Maybe you can at least 
>split it up  
>on a per namespace basis (perhaps using the fragment part of 
>the uri of  
>the namespace)?
>It surprises me none of the JEP-0060 authors are replying (or 
>those of  
>JEPs depending on it, like 0084 and 0118). At least a security  
>consideration could be added to them.
>Anyway, Magnus, if you use this in your client it look secure to me,  
>provided the problem of deleted pubsub nodes is taken care of.
>Standards-JIG mailing list
>Standards-JIG at jabber.org

More information about the Standards mailing list