The discovery error you are seeing is somehing very odd. For all practical purposes, that error is indicating that the service discovery handler never got set up. (or at least never got set up before it was accessed) It's like the first thing that the transport setups up when PyTransport is initialized though. Color me confused how it would not be there. Could you provide -D logs ... you could do this:
./PyAIMt -D -l mylogfile and then send mylogfile directly to me? Censor passwords if you are worried about that. BTW, when you say component, what do you mean? Is this a component much like the transport itself? Or is this effectively a client? or? =) Daniel On Jul 19, 2006, at 8:26 PM, Matthew Anderson wrote: > Okay, so my example doesn't quite work, as of course: > > <iq xmlns='jabber:client' type='get' to='aim.bebop' from='bebop' > id='iv8c1us1'><query > xmlns='http://jabber.org/protocol/disco#info'/></iq> > > Is an incoming service discovery request, not output from my > component. Somebody isn't paying close enough attention to what > he's copying and pasting (or needs some more sleep). The thought > is still an interesting one though -- what would cause that message > in the traceback? > > Still working on it, > > -- > Matt Anderson > > > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
