http://wiki.squid-cache.org/RequestQueues

Just thinking about how to handle processing HTTP requests, replies and
HTTP messages after my initial storework modifications. This stuff would
lead itself to look like "clientstreams" but with all the messages
abstracted out. It'd make it much easier to stuff processing in the middle.

This sort of thing should be implemented with threading in mind. There's
well-understood producer/consumer lockless queue implementations available
for single thread reader/single thread writer situations which leads
itself to this kind of thing.

Comments?



Adrian

Reply via email to