On Tue, Mar 3, 2009 at 9:17 PM, joeuser <[email protected]> wrote: > Thanks Norman, I'll apply the update. BTW I would have sent the debug > information to you sooner but the transport hasn't dropped offline > since I enable dumpProtocol. I'm a little unclear about what triggers > the problem. Does this mean that a gajim client may have been causing > it to fail? >
No worries, my transport crashed for the first time today with the same problem, so I was able to get a dump of the xml. The bug was caused by Google Talk sending some extra data, that xmpp.py didn't know how to handle correctly, combined with stricter checks in the newer version of jabberd2. Gajim uses the same xmpp library that the transport uses, so I checked to see if they'd come across the same problem, and they had, so I copied their fix :-) It's interesting that the extra bit of data is xmlns:ses='yahoogoogle:session' - I wonder if this means some sort of GTalk/Yahoo integration coming soon. -- - 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 -~----------~----~----~----~------~----~------~--~---
