I agree with Ber completely, and I reported this before too. My experience that most users are unique, and hence caching of css is not applicable. As a result, .css files are real bandwidth wasters (at one point drupal.css was 12% of my bandwidth, with 8% going to my theme's style). As a sort of workaround, I compress the CSS from drupal.css as well as from my theme, using one of these: http://www.cssdrive.com/index.php/main/csscompressor/ http://cdburnerxp.se/cssparse/css_optimiser.php I keep the original around or course, in case I need to make modifications, diffs with newer releases, ...etc. On 1/5/06, Bèr Kessels <ber@webschuur.com> wrote:
Op donderdag 05 januari 2006 14:58, schreef andre:
CSS files are, of course, cached client side on the very first page view and *Shouldn't* be downloaded time and time again. Yes they can be large - and could use some pruning - but its not a real performance issue.
I reported this before too.
ON my server, apparantly, 75% (more even) is a one time visitor. Drupal.css is always in the top 10 of most bandwith eating files.
But too much has been said about this. I beleive nothing will happen to that drupal.css file. All threads, all patches, all projects on this died in a heated debate. We will have to get to live with it :) /end music
bèr