Marc Dirix wrote:
threading is better suited for memory management and limitation.
How's that exactly? Using unix fork() which is copy on write, forking
many processes tends to be very memory efficient.
threading is more controllable during a DoS attack.
I've never heard this before, please expound.
threading if done right, will provide better scaling abilities (see
roxen versus apache).
I don't know much about roxen, but I think lots of things will scale
better than Apache since Apache by design is a kitchen sink type program.
threading will provide us eventually with a more sleak and clean design,
because it does not allow for the apache programming model in the sense of:
"We have this child, it leaks memory so lets kill it after x connects en
start a new one."
This sounds like a threads are better because they are argument. The
benifit of being able to kill off a process with memory leaks is that
the server still runs, if you have the same memory leak in a treaded
app, you have to restart the whole server.
I'm not against threading, I'm just concerned that we are going to add a
ton of complexity for very little gain.
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
