One of the main benefits of using CSS in general is that its cached locally in the user's browser. On the first visit there is some overhead, but subsequently (if its is acting properly) the browser shouldn't request a new stylesheet if it has one of the same name in its local cache.
This is true, when the file is served by the server. It sets the appropriate headers. Has anyone even inspected HTTP headers sent by a Radiant response? There is no Cache-Control header, no Expires, Last-modified or Etag, too. Yes, the browser will cache such kind of content, but not for long (depends on the browser). The result is all your users polling the stylesheets all the time because their browsers try to validate their internal cache, but don't have the means with (like an Etag).
For the people not knowing what the hell I'm talking about, here is a good read:
http://www.mnot.net/cache_docs/
People with big stylesheets and traffic running Radiant move their styles to a static file, anyway. Maybe they want to edit it with a proper editor - yeah I know TextMate can edit content from web textboxes, but not all people have fancy Mac boxes. Maybe they want it served (and cached) properly - by a web server. So you've moved your styles to external files, great. What now? Can you make quick changes to them inside the admin interface? Not really, you've sacrificed that. So, what I asked before was do we really need to sacrifice that, having such a flexible and powerful framework?
_______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
