My outstanding theory is one that is a pain in the absolute butt to investigate. =( Basically my theory is that oscar.py is overwriting some variable that the underlying mechanism uses as of probably Twisted 2 and that variable controls some sort of queue or something along those lines. That's the only thing I can come up with that would explain why it doesn't happen in Twisted 1, does in Twisted 2, and only happens to AIM/ICQ. (note that folk haven't seen the behavior in PyMSNt as far as I've ever seen) I started actually planning on bundling Twisted 1 at one point.
Daniel On Jun 3, 2007, at 9:38 AM, Chris Carlin wrote: > I'm trying to track down this longstanding delayed messages bug > associated with pyaim-t. As may have been said before, I can see the > message being handed over to twisted (transport.write), and I can > verify > that the traffic is delayed with tcpdump. > > tcpNoDelay is set to true to disable Naugle's algorithm, but that's > about all I can think of to do. It really does look like a buffering > issue, though. > > Do the other transports experience this delay as well? Anyone have any > thoughts on making Twisted behave? > > ~Chris > _______________________________________________ > py-transports mailing list > py-transports@blathersource.org > http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports _______________________________________________ py-transports mailing list py-transports@blathersource.org http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
