Slashdot Mirror


Is XMPP the 'Next Big Thing'

Open Standard Lover writes "XMPP (eXtensible Messaging and Presence Protocol) has been getting a lot of attention during the last month and it seems that the protocol is finally taking off as a general purpose glue to build distributed web applications. It has been covered that AOL was experimenting with an XMPP gateway for its instant messaging platform. XMPP has been designed since the beginning as an open technology for generalized XML routing. However, the idea of an XMPP application server is taking shape and getting supporters. A recent example shows that ejabberd XMPP server can be used to develop a distributed Twitter-like system."

13 of 162 comments (clear)

  1. buzzwords are my favorite by User+956 · · Score: 5, Funny

    XMPP has been designed since the beginning as an open technology for generalized XML routing. However, the idea of an XMPP application server is taking shape and getting supporters. A recent example shows that ejabberd XMPP server can be used to develop a distributed Twitter-like system.

    Minus two points for not managing to cram the phrases "AJAX" or "Web 2.0" into this writeup.

    --
    The theory of relativity doesn't work right in Arkansas.
    1. Re:buzzwords are my favorite by Rogerborg · · Score: 5, Funny

      Wash your mouth out with SOAP. Everything is a Web 2.0 technology.

      --
      If you were blocking sigs, you wouldn't have to read this.
    2. Re:buzzwords are my favorite by TheRaven64 · · Score: 4, Interesting

      Why not? The web is basically a way of sending XML to users. XMPP is a way of sending XML to users. AJAX is an ugly hack. It's fine for sending data from the client to the server, but to get updates from the server you need to keep polling. With XMPP, the server can push XML fragments to the client whenever it wants and some client-side JavaScript could then process them into the DOM. There was a proof of concept a few years ago (before AJAX was a buzzword) where someone integrated an XMPP client into a web browser and used it to deliver updates to the page.

      --
      I am TheRaven on Soylent News
  2. Am I too late... by abigsmurf · · Score: 4, Interesting

    To try to standardise how this is pronounced? eg. "wizzywig", "scuzzy" etc.

    'Zemp' would be a nice easy way of saying this.

    1. Re:Am I too late... by Anonymous Coward · · Score: 5, Funny

      "ex-em-pee-pee"?

    2. Re:Am I too late... by Bogtha · · Score: 4, Informative

      A lot of people pronounce it "Jabber". The name "XMPP" arose when they were moving it through the IETF standardisation process.

      --
      Bogtha Bogtha Bogtha
    3. Re:Am I too late... by TheRaven64 · · Score: 4, Informative

      Speaking as someone whose frustrated with having to implement two code paths in a Jabber client - one for the standard and one for the compatibility with Pidgin - I'd be very happy for Pidgin users to stop connecting to the XMPP network.

      --
      I am TheRaven on Soylent News
    4. Re:Am I too late... by mhall119 · · Score: 5, Insightful

      Wouldn't it be easier to just make the fix in Pidgin and submit a patch?

      --
      http://www.mhall119.com
  3. XMPP as a silver bullet? by webword · · Score: 4, Interesting

    One thing often overlooked by people is that is kills vendor lock. There are several government agencies which use a proprietary messenging system for instant messenging. Once you introduce true XMPP-compliant products, this kills the stranglehold that some of these vendors have. I'm sure this is true outside the government too.

    1. Re:XMPP as a silver bullet? by rindeee · · Score: 4, Informative

      Bzzzt...wrong. All IM in Gov/DoD is IRC based but moving to Jabber. This is public knowledge (not even U/FOUO). Lot's of commercial development going on around this if you Google around a bit. Some really cool stuff in the pipeline, especially where XMPP is concerned.

  4. Thanks Google by tmalone · · Score: 5, Insightful

    Say what you will about Google and privacy concerns, but this is one case of Google doing something good. If they hadn't used Jabber/XMPP for Google Chat, I doubt that we would be seeing this level of interest from others. Just about everybody that I chat with uses Google Chat now, and so, for the first time they all use Jabber capable clients. This is a very good thing. If Google goes out of business, or just becomes unpopular, the infrastructure will now be there to somewhat effortlessly transition to a new dominant IM system that is based on open standards, instead of going back to the days of MSN, AOL, Yahoo, and ICQ, all fighting each other and their users.

  5. Re:Just what we (didn't) need !! by Enleth · · Score: 4, Informative

    Have you ever actually SEEN this protocol in action, its specifications, functionality and security features? This is one of the few cases where XML is actually a proper, well-implemented technology suitable for the job. I've been using Jabber as my IM of choice for a few years already, and XMPP as a communication platform for a few non-IM projects and all I can say is that the people involved in its design got it right and created a really flexible, adaptable and secure technology.

    Yeah, I know, this is Slashdot, where people like to spew completely uninformed pseudo-opinions, but this one is just too obvious. Well, happy IMing on unencrypted, stone-age, propertiary networks that force-feed you with ads and censor your messages, if that's what you want.

    --
    This is Slashdot. Common sense is futile. You will be modded down.
  6. Re:XMPP is a PITA by Enleth · · Score: 5, Informative

    That's just this library. For example, the Smack API for Java is literally five lines of actual code to connect, announce the presence, load the roster and send a message. PyXMPP is quite low-level for a Python network library. Try XMPPy, much easier to work with if you need Python.

    --
    This is Slashdot. Common sense is futile. You will be modded down.