Daniel Henninger wrote:
This is unfortunately a known issue that appears to only occur in
Twisted 2.0 on up. It's fine in Twisted 1. Basically what happens is
your message is delayed until the next message goes out to AIM's
network. So if you think of all of the messages going to AIM as a
queue, it's always "one step behind". I've yet to figure out what
causes it as I can watch the handling enter and leave my own code and go
out into twisted core functionality. I believe it's my code that's
somehow causing the problem, but without the delay showing up in my own
code, it's hard to track down. My theory is that I'm overriding some
variable that is used by twisted core and am confusing it. Still,
haven't had more time to investigate and kept getting nowhere with it.
Interestingly enough, using the epoll reactor appears to solve the problem.
Daniel
Have you ever asked the Twisted guys, BTW?
~Chris
_______________________________________________
py-transports mailing list
[email protected]
http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
