News for hackers. Stuff that matters.
Re:WebSockets: caution required by boggzPit on Thursday December 31, 2015 @02:31PM (#10819210)
Why was RabbitMQ not great as a backend?

I am curious because we use it for a not launched chat application (+websockets) currently and we are not sure if it will hold big amounts of users.

Re:WebSockets: caution required by bradgessler on Thursday December 31, 2015 @03:36PM (#10819553)
I found that it was difficult to deal with a web client connection dying, then reconnecting, and recieving messages it may have missed while disconnected. There's a flag you can set for this in Rabbit when creating a queue, but I couldn't really get it to work.

The way Firehose works the client gets a sequence ID per channel that's always counting up. If the connection drops when the client is on sequence 1, then 4 new message come in, and the client reconnects, it will get the rest of the messages up to sequence 5 and wait for new messages.