Hi!

To implement the XEP-060, I'd like to have a running example which would also
serve as a tool for evaluating the progress.

Here are my notes for it, please comment on it.

Bernd came up with something like Twitter. That would mean we have a node per
person (for example [email protected]/tweets) to which other people can
subscribe.

Whenever I publish a message on my pubsub node, every subscribed person is
notified of my message (Publish an Item to a Node 7.1).

This basic setting includes many of the features defined in the XEP-060.  We
need the possibility to have an "open node" where everyone can subscribe
without authorization, and we need some authorization mechanisms if users don't
want to allow everyone per default (covers Affiliations 4.1 and Subscribing to
a Node 6.1, and Unsubscribing 6.2).

We need means of creating, configuring, and deleting nodes (covers important
recommended features 8.1, 8.2, 8.4).

The specification requires us to add discovery mechanisms (which features are
supported - Discover Node Information 5.3).

I think it makes most sense to start with a "persistent", "payload-included"
node. This means every subscriber can browse through old messages and a
notification of a new message also includes the message.

Note that this architecture ensures that everyone has control over his/her
messages and downtimes of a single server don't affect others.

Of course some features of Twitter won't be easily included. For example
there is no way to share one's subscriptions with other people (at least
not within XEP-060).

Concerning tool support: I don't know many Jabber/XMPP clients that support
XEP-060, but there is at least one node-management tool[1] available. Early
versions of the extension will be more or less static configured.

But let's get started with baby-steps. I'd like to have a request patched
through to a mock object of the extension. I'll take my inspiration from the
already included XEPs, but Bernd, if you have suggestions for an easier entry
tell me ;)

What do you think,
Michael

 1: http://x60br.berlios.de/

Reply via email to