[Citadel Development] (no subject)

[Freakdog]

 

Wed May 11 2016 05:31:46 PM EDT from IGnatius T Foobar @ Uncensored

The very bottom layers of webcit-ng are taking shape. It is so refreshing to be able to throw away code that implements assumptions and requirements from 20 years ago. The new code requires no per-thread state, since it's not descended from code that was, at one time, not a worker thread model.
Threads simply spawn when load requires it and accept connections forever until the server is killed. Threads enter the worker loop knowing nothing but the socket on which they are listening for connections. One thread wakes up on a connection, does its work, and then loops back and is ready for another connection.

Every layer is being built well before proceeding up to the next one. The current implementation doesn't even speak HTTP yet.

So, no cleanup if there's no connections after a period of time. Any thoughts on settings for minimum or maximum worker threads?