3 ms·
The client interface is up to you, but no need to re-invent the serverside part: From http://xmpp.org/extensions/xep-0124.html http://xmpp.org/extensions/xep-0
by tdfx 16y ago
The client interface is up to you, but no need to re-invent the serverside part:
From http://xmpp.org/extensions/xep-0124.html http://xmpp.org/extensions/xep-0124.html
This specification defines a transport protocol that emulates the semantics of a long-lived, bidirectional TCP connection between two entities (such as a client and a server) by efficiently using multiple synchronous HTTP request/response pairs without requiring the use of frequent polling or chunked responses.
Drop in an existing XMPP chat server (or write your own if you must) and you should be good to go. A lot of high-volume sites are using this implementation for their web-based chat services.
- tdfx 16y agoAs an aside: If you're not willing to make that substantial kind of change to your system at this point, I would at least recommend basing your messaging system on something that's designed to do it (i.e. a message queue) as opposed to a relational database. RabbitMQ has had quite good reviews from what I've seen, with clustering and persistence available.