pyicq in da house

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.

4 Responses to pyicq in da house


Comments

  1. Comment by Lukáš ‘Spike’ Polívka | 2008/01/13 at 10:26:00

    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.

  2. Comment by Steve | 2008/01/14 at 11:40:08

    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.

  3. Comment by Loreto Parisi | 2008/01/18 at 18:56:57

    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.

  4. Comment by Steve | 2008/01/22 at 14:46:16

    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.


Comments are closed