[ejabberd] AtomPub interface

Pablo Platt pablo.platt at yahoo.com
Sun Jun 22 02:21:12 MSD 2008

I think that to make pubsub useful in the real world
it has to work with "Result Set Management" http://www.xmpp.org/extensions/xep-0059.html
I don't think building a twitter clone with ejabberd is possible with the current implementation.
What if I want to watch posts 100-110 of a user that posted 1000 posts?
Result Set Management will be useful in many other scenarios like paging through 
the user list in a server that has thousands of registered users...
In my opinion paging is a must!

----- Original Message ----
From: Christophe Romain <cromain at process-one.net>
To: ejabberd at jabber.ru
Sent: Saturday, June 21, 2008 10:19:52 AM
Subject: Re: [ejabberd] AtomPub interface

> 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'
  <pubsub xmlns='http://jabber.org/protocol/pubsub'>
    <items node='princely_musings'>
      <item id='368866411b877c30064a5f62b917cffe'/>
      <item id='4e30f35051b7b8b42abe083742187228'/>

actual pubsub implementation does not handle that case anyway
ejabberd mailing list
ejabberd at jabber.ru

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jabber.ru/pipermail/ejabberd/attachments/20080621/239e33e7/attachment.html 

More information about the ejabberd mailing list