Show HN: Nchan – a pub/sub server as an Nginx module

Post by solyaris » Mon, Dec 07, 2015, 9:48 AM UTC

slact wrote: post #38

sams99 wrote: post #36

Earlier quoted context omitted.

nice! I initially stayed away from lua due so I could support earlier redises, but these days I would totally take that dependency on to simplify the code. regarding that implementation, one diff I am spotting is that I also have a concept of global message id / global channel, this allows us to subscribe to a single spot and distribute from there (which keeps thread counts down and is particularly useful for server…

> global message id / global channel Yeah, I don't have global ids. every message is bound to the channel it was published to. But I do understand that for your use case, (user + arbitrary list of groups), you'd need a good deal more than 4 channel multiplexing. It's a pretty strong use case and I'll see what I can do in the next month. Of course, I can be incentivized to work faster with a generous donation :) > Reg…

Post by slact » Mon, Dec 07, 2015, 4:26 PM UTC

ende42 wrote: post #39

slact wrote: post #32

Earlier quoted context omitted.

Well, if it ain't broke, as they say... here's a page on the differences between Nchan and the Push Module: https://nchan.slact.net/upgrade . One important thing I forgot to add is that the Push Module suffered from memory fragmentation under high load, and with a fixed-size shared-memory chunk that could mean running out of usable shared memory for a long-running nginx process. If you're not experiencing that, and y…

Thanks for the upgrade link. I missed that. Great that NCHAN is (almost; besides directive prefix) configuration compatible! The "Subscribers" section of "Push Module" should include websocket, I think.