A long time ago I encountered a little hiccup:
http://renegademinds.com/Home/Blog/tabid/60/EntryID/30/Default.aspx
That's a symptom of a different problem -- It's a bad idea to allow compression for compressed files.
Compressing files on the fly disables the ability of a server/client to calculate the download time. For a web page, this isn't really important, but for a large download of several MB or many MB or even GB, this is an increasingly serious problem.
In layman's terms: When you see a download that has no calculated time estimate for the download, THIS is the problem.
But I'm still seeing this configuration problem at different "tech" sites.
I don't consider myself a guru in this area, so I'm surprised that so many sites still compress files on the fly that they shouldn't be.
Is anyone else seeing this? Or am I just noticing it?
http://renegademinds.com/Home/Blog/tabid/60/EntryID/30/Default.aspx
That's a symptom of a different problem -- It's a bad idea to allow compression for compressed files.
Compressing files on the fly disables the ability of a server/client to calculate the download time. For a web page, this isn't really important, but for a large download of several MB or many MB or even GB, this is an increasingly serious problem.
In layman's terms: When you see a download that has no calculated time estimate for the download, THIS is the problem.
But I'm still seeing this configuration problem at different "tech" sites.
I don't consider myself a guru in this area, so I'm surprised that so many sites still compress files on the fly that they shouldn't be.
Is anyone else seeing this? Or am I just noticing it?
