[ejabberd] AtomPub interface

Christophe Romain cromain at process-one.net
Sat Jun 21 11:19:52 MSD 2008


> 2. One thing that lacks in XEP 60 to make the bridge better is a way
> to address a single item in a node.
> We can get the last item, all the items, but not only one item through
> its identifier.
> Is this by design ?

hum, i guess chapter 6.4.5 is what you said.
A service MAY return event notifications without payloads (e.g., to  
conserve bandwidth). If so, the client MAY request a specific item  
(using the ItemID) in order to retrieve the payload. When an entity  
requests items by ItemID, implementations MUST allow multiple items  
to be specified in the request.

Example 73. Subscriber requests specific items by ItemID

<iq type='get'
     from='francisco at denmark.lit/barracks'
     to='pubsub.shakespeare.lit'
     id='items3'>
   <pubsub xmlns='http://jabber.org/protocol/pubsub'>
     <items node='princely_musings'>
       <item id='368866411b877c30064a5f62b917cffe'/>
       <item id='4e30f35051b7b8b42abe083742187228'/>
     </items>
   </pubsub>
</iq>

actual pubsub implementation does not handle that case anyway


More information about the ejabberd mailing list