3 ms·
Well, unless it's doing something exceedingly clever, it looks like it will be launching one process per connection. For communication servers, this could prov
by dpwm 8y ago
Well, unless it's doing something exceedingly clever, it looks like it will be launching one process per connection.
For communication servers, this could prove a challenge – you'll probably want to use some kind of pub-sub architecture. By the time you've gone down that road, you could've gone down one of the more robust paths.
Still, this looks great for smaller apps. And, it seems a great way to prototype – especially if your favourite language doesn't have great websocket support.
- loeg 8y ago> Still, this looks great for smaller apps. And, it seems a great way to prototype – especially if your favourite language doesn't have great websocket support. Totally agree. inetd is a pretty good model, it just falls down in the face of thousands of slow, low-computational effort connections tying up gigabytes of RAM. That and most schedulers seem to struggle with that number of threads.