9 ms·

XMPP library for node.js

• hammerdr 16y ago
  How is this different than http://github.com/mwild1/xmppjs http://github.com/mwild1/xmppjs ?
  • Rauchg 16y ago
    "You like Strophe.js? You bought a copy of Professional XMPP Programming with JavaScript and jQuery? You even want to use the same XMPP code for the web and node.js? Then you're wrong here: go to xmppjs."
    • papachito 16y ago
      I don't find his explanation very clear. Could you explain what's the difference?
      • aaronblohowiak 16y ago
        Objectives of node-xmpp: Use node.js conventions, especially EventEmitter, ie. for write buffer control Fast parsing, node-expat was written with this library in mind Support for both XMPP clients and components After authentication, leave trivial protocol bits to the user (later we could offer helpers for entity capabilities hashing, etc) The other library lets you connect as a component to a XEP-0114 compliant server
        • papachito 16y ago
          Thanks, I read that part too, it still assumes you know what a component is in XMPP which I'm sure most people don't. So it's basically an XMPP client and a "component" (whatever that is)?
          • aaronblohowiak 16y ago
            a component is something that plugs into the server that can receive messages on the domain and reply as anybody
• mahmud 16y ago
  Gaah, that's like hitching a trailer to a Lamborghini. The point of XMPP is to be fat and semi 'standard' complaint. The purpose of node.js is to be fast, at the expense of compatibility and compliance, while maintaining the simplicity of javascript. If you want XMPP, it might be better to speed up any of its existing servers, instead of saddling Node with cruft.
  • frognibble 16y ago
    It looks like a nice library for writing non-blocking XMPP clients and components in Javascript. This seems useful even if the goals of XMPP and Node are different as you claim. This library does not saddle Node with anything. It's a library for use with Node. It's not part of Node
    • mahmud 16y ago
      The point of XMPP clients is to work with a server/platform infrastructure that someone else has built and has control over. Then, it makes sense to use something like Strophe.js to talk to the server in its protocol of choice. However, if the server you're talking with runs Node.js, there is a good chance whoever behind it (if not you) is someone who is able to make sane technical decisions, like not using XMPP and opting for something light weight. The way I see, and to use another anology, is like writing a SOAP server in assembly in the hopes of getting better results. If you want to talk with the myriad of desktop jabber clients out there, use something tried and true, and supports XMPP to the fullest (so Node is out.) If you just want a serialization and pub/sub protocol, use something more lightweight than XMPP. XML manipulation will defeat the purpose of Node, which is performance and design hygiene, very quickly.
      • vetinari 16y ago
        It is XMPP client, even if used server-side. You still need XMPP server to talk to (ejabberd for example).
      • DennisP 16y ago
        Sometimes XMPP is a requirement. Maybe you want the federation, or you want people to be able to use their gtalk accounts. Call me crazy but I actually think a non-blocking server with good performance and low memory usage would be a pretty nice foundation for an XMPP server. (This project is a client though.)
• papaf 16y ago
  I imagine this could become part of a non-blocking google wave server...