On Sat, 13 Sep 2008 11:02:11 -0300 Michael Caplan <michael@xxxxxxxxxxx> wrote: > 1. the gzip content encoding happens on the entire body before it is > chunked. > 2. the ungzipping happens on the entire body after it is dechunked. Exactly. > If I got this right (which I don't think I do), the web server would > need to first dechunk data produced from a dynamic source (PHP) > before it can apply the gzip content encoding. Why would PHP want to concern itself with chunked encoding? That's the business of the webserver, not the application. > Likewise, on the client end, it would only be able to begin > interpreting HTML following receiving the entire chucked payload, > dechunk it, and then ungzip it. You don't need the entire contents to start displaying it. Unless you rely on something whole-document, like parsing to a DOM. > But, that seems contrary to what Apache + mod_deflate actually does, What seems contrary? Read up on the apache filter chain. That's the basis for ordering different encodings, and indeed other transformations from content manipulation like SSI or XSLT through to SSL. -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.apachetutor.org/ --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|