On 31/08/2007, Anthony Ettinger <[EMAIL PROTECTED]> wrote: > > > On 8/30/07, Alfie John <[EMAIL PROTECTED]> wrote: > > > > However, if your CSS files are purely static, they shouldn't be > > handled by mason in the first place. > > > > Alfie > > > They are static files, but I only want one request to load all css files. > Which is why I am writing a mason component that spits out all css files > concatenated.
I agree with Alfie. Therefore, you should look at concatenating all the relevant CSS files in your build/deploy script and then let webserver handle the static serving of the single file. If you're not doing anything dynamic with Mason in the CSS then just let webserver do what's it's good at and just create it the once instead of dynamically many times. This is *much* easier than doing what you suggest on every request. Andy -- contact: Andrew Chilton website: http://kapiti.geek.nz/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
