On Thu Apr 29 18:08:46 2010, Laurent Eschenauer wrote:
We are solving this a different way in onesocialweb and this could
become an extension to PEP and/or PubSub. Here is the flow:

- User subscribe to a node (e.g. urn:xmpp:microblog:0) with a bare JID - Event messages are sent to the bare JID and have a new type (e.g. pubsub)
- The server does not forward the messages to connected resources,
instead, it puts the message in the 'PEP Inbox' (a pep node to which
only the owner has access)
- Clients interested in that content, subscribe to the PEP Inbox using
presence based subscription


Okay, so let me see if I follow.

Conceptually, then, this is the user's account itself subscribing to a remote PubSub node, and then the user's clients are then subscribing to the user's own PEP node which acts as an aggregator?

From an implementation standpoint, this means the server has to look inside messages inbound to the bare jid. I'm not *wholly* against this, because these are fairly rare, comparitively - in fact, I think the vast majority of such messages I get are already identi.ca ones - but in general I'm not keen on servers having to look "inside" without a type indicator, and I don't think adding a type is practical.

So instead, I'm thinking about whether a subscription type of "republish to me" is actually the way - ie, when I publish an item, my server republishes it to the PEP nodes of each subscriber in turn. (And yes, this technically isn't PEP as such anymore, it's some form of PubSub-onna-jid). The downside is that this means that the S2S traffic is now an <iq/> pair, but that does give us some form of reliability and error control.

What do you think ? Worth moving forward as an extension to PEP or
PubSub (e.g. PubSub inbox protocol). Is there other ideas/proposal out
there on the concept of a PubSub inbox ?

No, I do generally like the concept. I'm just wondering how to make it more palatable The thing I like more is the notion that this could unify the likes of status.net and onesocialweb - I think that in itself is pretty interesting.

Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
 - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
 - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

Reply via email to