I'm a front-end developer rather than a back-end dev so this might explain my silly questions. "80% of the end-user response time is spent on the front-end", so says the YUI performance blog. Anything that can be done on the front-end to aid better performance is simply good practice.
The reason that I want to concatenate CSS into a single file is for performance reasons. Reducing HTTP requests is one of the best ways to speed up your website. http://developer.yahoo.com/performance/rules.html#num_http Using the @import statement does not concatenate the files. The use of @import is actually worse, from a performance perspective, than many <link> tags because files are downloaded sequentially rather than in parallel. Read Steve Souders blog for more info. http://www.stevesouders.com/blog/2009/04/09/dont-use-import/ Curtis Garman wrote: > > Why does it all need to be the same physical file? I would use the css > import statement to import your global.css as shown below and then > link the global.css file to your pages (as you mentioned)...this will > give you ability to seperate your css but avoid the bother with the > jsp includes. > > @import url(../global/i_base.css); > @import url(../global/i_header.css); > @import url(../global/i_footer.css); > @import url(../global/i_layout.css); > @import url(../global/i_button.css); > > -- View this message in context: http://www.nabble.com/How-to-use-Includes-in-CSS-files-tp26024235p26032674.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
