[crosspost from xmpp.py list] I have put together a first pass patch [1] at getting xmpp.py to speak the jabberd 2.0 Component Protocol [2].
I do not like the way I have hooked the dispatch event. I'm less horrified, by how I've mangled the send event. That being said, the patch *does* work (proven on my server with the yahoo transport). I would probably end up doing dispatch a similar way to send, and just move all the current dispatch code into a new method, which is called from the old one. My issues with this are speed (It's bad enough I had to mangle the send event this way). I guess in reality the dispatcher needs to be unplugged, and a new one needs to be inserted in the middle that handels the wrapping and unwrapping of packets to the router. All-in-all I think the jabberd2 protocol should be changed so you don't need route stanzas. (all the other commands should become standard iq, and presence stanzas) I'm open to comments, and suggestions, so please let me know. [1] http://www.darkskies.za.net/~norman/jabber/xmpp-jabberd2-component.patch [2] http://jabberd.jabberstudio.org/dev/docs/component.shtml -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ On 26/08/05, Norman Rasmussen <[EMAIL PROTECTED]> wrote: > ahh, yes, i did debug this, and now i come and read email.... > > I've managed to get it to take the binding *yay*, it was a matter of > sticking the namespace in right :-) also I found I have to use sasl, > and I can't use the old 'handshake' method to connect, does this sound > right? > > also moving from handshake to component, meant that I had to supply a > username, which I nailed down too. > > On 26/08/05, Stephen Marquard <[EMAIL PROTECTED]> wrote: > > Norman Rasmussen wrote: > > > I've been having at trying to get the yahoo-transport from the xmpp.py > > > project to work with this JEP....., here's my problem > > > > > > Is <bind> in the root namespace? > > > > > > for most componenents the default namespace is set to > > > jabber:component:accept, so this makes any bind calls occur in the > > > jabber:component:accept namespace too. > > > > The JEP says: > > > > The namespace URI for elements in this protocol is > > 'http://jabberd.jabberstudio.org/ns/component/1.0'. > > > > and from a j2 debug log (sm binding to router): > > > > <bind xmlns='http://jabberd.jabberstudio.org/ns/component/1.0' > > name='some.fqdn'/> > > > > > I'm trying to send (after the handshake, but before the disco results): > > > > > > <bind from="transport.domain" name="transport.domain" id="1" /> > > > > You don't need from and id. > > > > Regards > > Stephen > > > > _______________________________________________ > > jdev mailing list > > jdev@jabber.org > > http://mail.jabber.org/mailman/listinfo/jdev > > > > > -- > - Norman Rasmussen > - Email: [EMAIL PROTECTED] > - Home page: http://norman.rasmussen.co.za/ > -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ _______________________________________________ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
