Robert Collins wrote:
> orgin server -> our upstream socket
> socket to fs layer
> fs layer->list of listening clients
No. More like:
origin server -> our upstream socket
socket -> memory cache
memory cache -> list of listening clients
memory cache -> fs layer
listening client -> client socket
> Just to be clear. I'm going to set a tag te-20010104 for his old work, and my work will be on the te tag itself.
Perfectly fine.
> In fact what I'm going to do is
> te - core te header support, chunked encoding only, API for
> adding new chunking code (patricks code is somewhat modular, but not
> grouped cleanly enough to be plugin like fs or repl code is).
> te_compression - gzip/deflate support.
> te_whatever new algorithm.
If you make the API modular with a configure option for which encodings
to enable I see no need to have separate branches. But if you really
want to sure.
/Henrik
Received on Thu Jan 04 2001 - 23:33:46 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:13:10 MST