Today I replaced the good ol’ JIT Jabber ICQ Transport with PyICQ-t. JIT seems to fail for recent updates to the ICQ protocol and there seems to be no updates to fix the issues. So I decided to give PyICQ another try. Let’s hope it doesn’t eat up too much of our beloved resources (RAM, RAM, RAM). Please let me know of any issues.
svn co svn://mytlt.ru/jit
This one should be hot-fixed, but still not perfect.
If you don’t have thousands of (ICQ) users, PyICQt is better choice.
Thanks a lot, Lukáš. PyICQ works fine until now and memory consumption is at a decent level. I’ll stick with it unless this changes.
Hi, I’m a web developer. I wanto to thank you for your work first of all. Then I have a technical question. Look at the JavaScript code:
…
var p = new JSJaCPresence();
p.setType(’unavailable’);
p.setShow(’unavailable’);
p.setStatus(’Logged out’);
p.setPriority(127);
con.send(p);
// now, if I do …
con.disconnect()
…
In this case the presence won’t be sent to the Jabber server, so no logout will be done.
If I don’t call the disconnect, the presence will be sent correctly. Should I wait for a callback to send the disconnect after the logout presence or it’s not necessary, since I see on the server log the end stream tag in any way?
Thank you.
Don’t know what this has to do with pyICQ but anyway: Which JSJaCConnection type are you using? Http Binding or Http Polling? Which Jabber server are you using?
Actually if you’re doing a call to disconnect it sends a presence of type=’unavailable’ automatically.