Antwort: [Mod_gzip] mod_gzip without apache..?

[Dariusz Pietrzak]

> Hi Eyck,
Hi,

> mod_gzip is an Apache module; a big part of its code
> handles the internal Apache APIs.

based on that description:
"
mod_gzip adds HTTP compression to web server. Although it may be used
with any webserver (well, its authors say that ;-)), its Debian version was
prepared for using with Apache.
"
i thought that mod_gzip is just a generic way of adding compression..

> So I cannot imagine how you expect such an Apache dependent
> piece of code to work "without Apache".
in this case, this is probably still the best forum for my question: 
considering that such simple proxy is just few lines of code, how do you
add compression to it?
 Would you just gzip everything that goes through? ( what should you do
 to inform browser that what is coming is compressed? add header?
change mime-type or sth? )

> > That would be something like thise - simple proxy that passess
> > all requests on. Would it be hard to do? Does such solution
> > already exists?
> > request -> proxy -> real server
> > client <- proxy compressess response <- real server.

> And why should this "proxy" not be an Apache with mod_proxy
> and mod_gzip?
 Hmm, because i'm short on memory, and don't want to bring whole apache
for such simple task. When I'll be considering something for production
environment apache'll be way higher on my list...
 Also, seems like mod_gzip uses files for it's operation. I'd like
something working using some kind of streaming...
( like you can do tar -c | lzop | do something )

Hmm, is this issue really that complicated? I thought I'd find answers
quickly by looking at the source, but I found the source to be way
bigger then I expected, and handling way more possible options etc than
I thought is needed.
 Maybe there's some technical document that describes it's workings that
I've been missing?