Michael Jakl wrote: > Hi! > > On Thu, Apr 23, 2009 at 11:54, Bernd Fondermann <[email protected]> wrote: >> Michael Jakl wrote: >>> Until 2009-05-23 my plan would be to continue to explore the current Vysper >>> capabilities as well as to read the XEP-060 in detail. >> Since this is also the Community Bonding Period, do you have any idea >> how to get you out of your study and provide some feedback loops? > > I was thinking about that the last few days. Besides discussing > implementation details and providing code-examples (like my first > steps yesterday) I can't think of something. Of course, I participate > in discussions on the list (at least where I can add something ;)). Do > you have something on your mind? > >> I'd define two goals: Structure the spec for implementation (plan) and >> maybe summarize the parts to involve the rest of the community, so that >> they get an idea of what it's all about.
Creating documentation on confluence would be one possible approach. > I'll do that. Currently I'm in the middle of RFC3920, which is (as you > said it) absolutely essential for understanding Vysper/XMPP, after > that I'll have to reread some parts of XEP-0060. > > At the coding-front I've set up the handler for the IQ stanzas within > the pubsub namespace for "normal" pubsub stanzas and "owner" stanzas. > Although I haven't yet managed to set up a good test-environment for > me. > > For those not familiar with XMPP, at the top level are three types of > stanzas namely presence, message and iq. A stanza is nothing more than > a XML element exchanged between XMPP parties. The info/query stanzas > are very general and can have different types (like set, get, error, > and result). > > Publish/Subscribe operates within these iq-stanzas. The sub-elements > of the iq-stanzas lie within a specific namespace, which can be used > to "route" the stanzas. So far I've registered a handler for the > iq-stanzas for the pubsub-extension. > > Cheers, > Michael Bernd
