Thank you for your response Sam!
The way it happens, as I understand it, is this:
1 - your browser sends an 'Accept encoding' header.
2 - if that header says 'gzip, deflate' php zips up the file and sends
it off to you, zipped.
The log files on my server showed that compressed files were delivered.
In addition, and this is kind of interesting, the site I tested was
prone to a FOUC when I was testing; the Flash was notably
shorter-to-absent when the compression was enabled.
With regards to server processing, I bring up the 'download once and
cache' CSS argument - while using this method on every page is taxing to
a server (compared to mod_deflate or mod_gzip that will cache frequently
accessed compressed pages), here the idea is that it only happens on the
entry to the site when the CSS file is downloaded then cached.
hth (and I hope I'm right! ;-]) - Mike
Sam Carter wrote:
> I've put a post up on my new weblog about a technique that can be used
> for compressing CSS files if you have access to PHP but not Apache's
> mod_deflate or mod_gzip.
> I read your web page, and it appears to me that you've compressed the CSS
> file on your server, but expand it back to normal using server side PHP code
> when sending it to the client.
> If I read this correctly (I'm not PHP experienced), then you're saving
> server disk space at the expense of server cpu time - *and* there no savings
> in transmitted data since the CSS is fully expanded leaving the server.
> I'd like to know if I'm missing something. Hope this reply is read as it
> was intended - I'm just trying to follow the thought and don't want to
> appear critical.
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/