So I finally got around to switching from 0.6 to 0.7b and I realize now that I wasn't seeing precisely the problems Alexey was describing... but now I am!
Again, this is with ejabberd, which seems to delay the transport's initialization in a way that jabberd2 did not. I now see that 0.7b delays messages in ways that 0.6 didn't, though I have no personal experience between 0.7b's behavior in jabberd2 versus ejabberd. Ahhh, orthogonalities.... Anyway, another observation: often my messages will be sped up when a message is incoming. If I am seeing 20 second delay on outgoing messages and the other person sends a message, they will often receive one message immediately. I haven't a clue what this means. Could it be some sort of buffering you're not thinking about? Maybe some buffering feature of twisted that changed during the 0.6-0.7b upgrade? ~Chris Chris Carlin wrote: > Actually I switched from jabberd2 to ejabberd over the weekend and > noticed this behavior as well. I don't know what's going on, but I can > certainly tell that it was not happening before the switch and is > happening now. > > I haven't timed it, but it seems to take around half a minute to a > minute for the transport to show as online on my roster, and another > fifteen seconds or so for AIM contacts to show up. In all it may take > around a minute to a minute and a half for AIM contacts to show up > after the jabber connection is working. These times are all estimates. > > ~Chris
