Have you ever tested under ejabberd? Odd things had been happening since
I made that switch...
I'm on gentoo with the following versions:
dev-python/twisted-words-0.3.0 *
dev-python/twisted-2.1.0 *
dev-python/twisted-xish-0.1.0-r1 *
dev-python/twisted-web-0.5.0-r1 *
dev-python/twisted-conch-0.6.0 *
dev-lang/python-2.4.2 *
~Chris
Daniel Henninger wrote:
> I can't imaging what that might be. And again, I haven't seen a
> single difference on my side. =/ I mean there's certainly a lot
> that changed between 0.6 and 0.7. Wish I could see what you all are
> seeing on my own server... =/ Chris, what version of Twiste and
> Python are you using?
>
> Daniel
>
> On Jan 31, 2006, at 5:51 AM, Chris Carlin wrote:
>
>> 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
>
From [EMAIL PROTECTED] Thu Feb 2 01:27:36 2006
From: [EMAIL PROTECTED] (Daniel Henninger)
Date: Thu Feb 2 01:27:43 2006
Subject: [py-transports] delays in pyAIM-t and pyICQ-t
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
ejabberd, jive, jabberd2, and jabberd1. =) (and ejabberd is my
primary server) Running:
ejabberd 1.0.0
Twisted 2.1.0
Twisted Words 0.3.0
Twisted Xish 0.1.0
Twisted Web 0.5.0
Twisted Web2 0.1
Twisted Runner 0.1.0
Twisted Pair 0.1.0
Twisted Names 0.2.0
Twisted Mail 0.2.0
Twisted Lore 0.1.0
Twisted Flow 0.1.0
Twisted Conch 0.6.0
Nevow 0.5.0
Python 2.4.2
Running under RedHat Enterprise Linux 3. Besides that, I tried it
under:
Jabberd 2.0s10
Jabberd 1.4.3
Jive Wildfire ... forget the version
Also tried under:
Python 2.3.4
Twisted 1.3.0 (I believe s1 or something like that)
=/
Daniel
On Feb 1, 2006, at 8:19 PM, Chris Carlin wrote:
> Have you ever tested under ejabberd? Odd things had been happening
> since I made that switch...
>
> I'm on gentoo with the following versions:
> dev-python/twisted-words-0.3.0 *
> dev-python/twisted-2.1.0 *
> dev-python/twisted-xish-0.1.0-r1 *
> dev-python/twisted-web-0.5.0-r1 *
> dev-python/twisted-conch-0.6.0 *
> dev-lang/python-2.4.2 *
>
> ~Chris
>
> Daniel Henninger wrote:
>
>> I can't imaging what that might be. And again, I haven't seen a
>> single difference on my side. =/ I mean there's certainly a lot
>> that changed between 0.6 and 0.7. Wish I could see what you all
>> are seeing on my own server... =/ Chris, what version of Twiste
>> and Python are you using?
>>
>> Daniel
>>
>> On Jan 31, 2006, at 5:51 AM, Chris Carlin wrote:
>>
>>> 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
>>
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
>
