Interesting! I wonder if what's happening is that you are running into a race condition of sorts where you ask the transport something before it's even remotely ready for you to ask it? Anyway, yeah, if you have time, send me a debug log and I'll see what I can figure out. =)
Daniel On Jul 20, 2006, at 9:03 AM, Matthew Anderson wrote: > On Jul 19, 2006, at 10:46 PM, Daniel Henninger wrote: > >> 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? =) > > Yes, kind of like the transport itself. Connects to server using > the server's connection secret, can emit arbitrary XML fragments, > receives fragments addressed for [EMAIL PROTECTED] as well as > component.host. It is supposed to serve as a layer of abstraction > between persons on the network, so we can make more interesting > (but specific) fragment routing decisions. Functionality required > by a client (the organization with software requirements, not a > jabber client). > > One of the person-sets we want this to connect to is folks on AIM, > so, the component needs to associate one or more of the JIDs it > manages ([EMAIL PROTECTED]) with AIM screen names. > > -- > Matt Anderson > > > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
