3 ms·
But why do the otherwise-independent app server processes need to be sharing 'the' socket at all? If you're already going to be running the same app on more tha
by blasdel 17y ago
But why do the otherwise-independent app server processes need to be sharing 'the' socket at all? If you're already going to be running the same app on more than one machine, there's no reasons left to stick to port 80.
It seems like you're stuck on the idioms of Apache and 'real web-servers' (as you put it).
- audidude 17y agoIf you don't share the client sockets at a level that can distribute work to all of the processes you will get an unbalanced number of connection:keep-alives amongst the workers.
- blasdel 17y agoBut we have this nice little abstraction called HTTP! The app servers don't have to know anything about load balancing. You're persistently parochial in how you're approaching these things.