I've read about a lot of browser problems handling JavaScript zip-compressed resources.
http://support.microsoft.com/kb/871205 http://www.thinkvitamin.com/features/webapps/serving-javascript-fast Are you sure to don't have side effect enabling compression by default? - Paolo On 2/8/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Hi, There's a pretty simple optimization we can do to have all our javascript and css contributions use CompressedResourceReference by default. The zipped contents are cached, so it is only computed when a fresh resource is requested (typically doesn't happen unless you change the file). And it makes a huge difference (e.g. that new YUI calendar thing I added this weekend went from 92kb to 18kb). Even though in production setups, you might configure your server to do this for you, if we do it at this really minimal cost, we're sure it happens for at least the common cases. Any objections?
