What about setting the content expiration in the HTTP headers, you can do this from within the webserver. Isn't that how it was intended to work?
Taco Fleur - Pacific Fox an industry leader with commercial IT experience since 1994 . http://www.pacificfox.com > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of russ - maxdesign > Sent: Monday, 19 September 2005 12:08 PM > To: Web Standards Group > Subject: Re: [WSG] The Big Lie about CSS > > > There is a simply option: > > 1. add a link to a generic css file: > <link rel="stylesheet" href="basic.css" type="text/css" > media="screen, print"> > > 2. inside this file, import any css file you need: > @import "advanced.css"; > > The advantages are: > 1. by using two media types in first link you will stop NN4 > from following the link and (in specific NN4 cases) from > crashing on the @import. > > 2. you can update the css file or files in the basic css file > any time you like without touching the html files - the > original lionk will always be the same. > > 3. you can make the @import css files modular and change as > needed. The basic.css file could include a range of imported > css files: @import "header.css"; @import "nav.css"; @import > "content.css"; @import "footer.css"; @import "colors.css"; > > Russ > > > > > > Well, that's the point of my trick, unwieldy though it is. > > ****************************************************** > The discussion list for http://webstandardsgroup.org/ > > See http://webstandardsgroup.org/mail/guidelines.cfm > for some hints on posting to the list & getting help > ****************************************************** > > ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
