Hi Norman, Could you please give me a hint about possible place of this "disco" implementation in the transport, so that I can fix this on my own to make it work with our server. It would have helped me a lot in fixing this problem on our side if you direct me to the place.
Thanks a lot for your quick responses, and I am sure this is one of the most active community. best regards, -Pravin. On Aug 29, 10:27 pm, "Norman Rasmussen" <[EMAIL PROTECTED]> wrote: > On Fri, Aug 29, 2008 at 5:14 PM, Sinha <[EMAIL PROTECTED]> wrote: > > We have our own XMPP compliant server product, It behaves properly > > with other gateways and gets the disco. > > Your server sends: > > DEBUG: socket got <iq from='[EMAIL PROTECTED]/sinha' > id='_19f35f92.11c0e1ca12f._7ff4_2120836081' lang='en' to=' > yim.india.myorg.com' type='get'> > <query > xmlns='http://jabber.org/protocol/disco#info'/<http://jabber.org/protocol/disco#info%27/> > > </iq> > DEBUG: dispatcher ok Got jabber:component:accept/iq stanza > > where as jabberd2 sends: > > DEBUG: socket got <iq xmlns='jabber:client' type='get' to=' > yahoo.jabber.example.net' from='example.net' id='q1zeajo3'> > <query xmlns='http://jabber.org/protocol/disco#info'/> > </iq> > DEBUG: dispatcher ok Got jabber:client/iq stanza > > notice the different namespace. > > I can't check what ejabberd and openfire and jabberd1 send, but I'm guessing > it must be jabber:client too. (otherwise disco wouldn't work there either.) > > xep-0114 seems to indicate that you are correct, and that existing code is > wrong. xep-0225 isn't very clear about what the namespaces of the > message/iq elements should be. jabberd2's component [1] protocol thinks > they should be jabber:client fairly clearly. (but that's only used when > route-wrap is enabled) > > [1]http://jabberd.jabberstudio.org/dev/docs/component.shtml > > -- > - Norman Rasmussen > - Email: [EMAIL PROTECTED] > - Home page:http://norman.rasmussen.co.za/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "py-transports" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/py-transports?hl=en -~----------~----~----~----~------~----~------~--~---
