Anthony Baxter wrote:
> A thread-per-request model is going to be simpler to code
> and work with, but it really does require splitting squid
> up into smaller components, to push things like the file
> i/o out of the main code.
And in large requires a total rewrite of everyting. Squid is currently a
event driven application, and turning this into a well designed and
efficient multithreaded application is not worth the effort. I'd rather
start from scratch than try to push the current Squid code into a
multi-threaded model, and use the current Squid code as source for ideas
on how to handle expiration, protocol conversions and such.
--- Henrik Nordstr�m Sparetime Squid HackerReceived on Tue Feb 03 1998 - 14:20:38 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:38:46 MST