Sadly, that's the problem. =( "Something is broken" with the twisted 2.* series. A couple of things seem to fix it:
1. using the epoll reactor 2. (using the select reactor instead of poll? not sure about this yet) 3. using twisted 1.3 instead =( Twisted 1.3 works fine. I'm 99.5% sure that "I've done something" to mess up my transports under Twisted 2. My guess is that I've overridden some important variable. Either way... damn hard to track down what's going on. =( =( Daniel On Jun 20, 2006, at 11:13 AM, Alexey A. Nikitine wrote: > Yes, I'm running Twisted 2.0.1 > My jabber server is Wildfire. > > Daniel Henninger wrote: >> Let me take a guess here... =) >> >> You are running Twisted 2.0.0 or newer? >> >> Daniel >> >> On Jun 20, 2006, at 10:45 AM, Alexey A. Nikitine wrote: >> >>> Hello. >>> >>> There is a strange bug in PyICQ-t. I observe quite a long delay >>> (about >>> 10 sec.) between receiving a message by a jabber server and >>> retransmitting it to the ICQ server. However, it relays messages >>> back >>> (from ICQ to Jabber) much faster. In addition, sending a message >>> from >>> ICQ to Jabber triggers those delayed messages to be sent to ICQ. >>> >>> Why does PyICQ-t work so strange? I tried both 0.7b and SVN. >>> >>> Thank you. >>> >>> -- >>> Alexey Nikitine. >>> >>> >>> >>> >>> >>> _______________________________________________ >>> py-transports mailing list >>> [email protected] >>> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports >> >> _______________________________________________ >> py-transports mailing list >> [email protected] >> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
