On Tue, 5 Dec 2006 13:29:43 -0500
Daniel Henninger <[EMAIL PROTECTED]> 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 think this is sometimes (not always...) the case with PyICQt, too.
I'm on twisted 2.x, 2.4 iirc.  If I have some time, I might have a look
at the code, but probably not anytime soon.

Regards,
Milan

--
Milan Holzaepfel <mail(a)mjh(d)name>             <URL:http://mjh.name/>
pub  4096R/C790FC23  EB8E 5E81 81E3 53A9 9B74  B895 5179 54C0 C790 FC23

Attachment: pgpFUS3TvhAbF.pgp
Description: PGP signature

_______________________________________________
py-transports mailing list
[email protected]
http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports

Reply via email to