Posted by guest at 2006-05-02 22:31:55
When I register with pyicqt, it gives me all subscribed-messages in blocks of
five messages (about 30 seconds break between them) and the jabberserver is
frozen until pyicqt is done. I'm using jabberd 1.4.3-3 (debian). I tried pyicqt
0.7a and the svn version (today), but that didn't make a difference.
To be sure it isn't (only) a problem of the jabberd I tried JIT - but JIT
works
without that problem.
Posted by jadestorm at 2006-05-02 22:38:59
Unfortunately, JIT currently gets around this problem by cheating, using a bug
that exists in jabberd. (or at least that's what I'm told) Unfortunately, I'm
not really aware of a great way to get around the subscription requests yet.
Going to try to see what I can do but yeah... it's quite a sore spot for us
gateway developers. =)
Posted by guest at 2006-05-03 09:09:43
I'm not sure if you got me wrong: The subscription messages are okay - but it
would be great if it wouldn't need 15 minutes to get all my contacts. (and
if it
wouldn't freeze jabberd until it's done). In other transports I get _all_ my
contacts at once...and not bit for bit.
Posted by jadestorm at 2006-05-03 12:19:32
I'm just saying that JIT is/was making use of something that wasn't as
'intensive' as what PyICQ is doing. It's possible that jabberd's karma
settings
are holding PyICQ back. Keep in mind that I don't know that for a fact, I'm
just speculating. Could you send debugging logs? (I've never seen this
behavior myself, not with jabberd1, jabberd2, ejabberd, or wildfire, so I can't
really begin to know what's going wrong without some logs) (-D is the
option to
add debugging, -l filename will send the debug output to a file) Thanks! (I
would recommend emailing it to me at jadestorm@nc.rr.com instead of posting it
here)
Owner: ---