3 ms·

I remember using XMPP for a site I built that connected tenants and landlords, a reverse MLS of sorts. Back then, I choose XMPP because I had heard this is what

I remember using XMPP for a site I built that connected tenants and landlords, a reverse MLS of sorts. Back then, I choose XMPP because I had heard this is what Facebook was using at the time for their new messenger and it provided services like online status, typing status, and live messaging out-of-the-box. I don't recall it being terribly difficult to implement and it was awesome to see it working for the first time! This was almost 10-years ago now, it's incredible to see this technology still moving forward.

k__ 5y ago
Interesting. I had the impression the general opinion about XMPP is that it's resented as the SOAP of messaging.
- dwaite 5y ago
  The primary similarity between the two is the use of XML. Maybe the general opinion is that XML sucks?
  - olau 5y ago
    It's just not a great protocol. Many years back I was working on a desktop client for XMPP. The first problem I encountered was that XMPP does not actually send individual XML documents each time it sends a message. Instead it starts with a tag that is not closed until you actually turn off your client and close the connection. So you couldn't use a simple XML document parser for those relatively simple messages as it would read the start tag and never finish, but had to do some kind of streaming-based thing.
- jasonwatkinspdx 5y ago
  This was my experience. It did end up doing what we needed and being able to use off the shelf libraries/servers at the time was convenient, but holy heck is the protocol chatty and annoying to debug at the trace level.