CSS files are cached (or not cached) just like any other piece of content normally.
However CF files send special directives instructing the browser not to cache them. Simple as that - the CSS isn't cached. And it makes sense: CF has no idea how understand when something is "good enough for now" - it always runs the code because the output might change. If you need your CSS dynamic (meaning it could change for each and every request) then this is definitely a simple way to do that. The question of whether doing this will be a performance issue is really dependent on your site and what it's doing. Will running an extra CF request for every page hurt you? However it sounds like you might NOT want your CSS to change for each and every request. If not why set it up to do that? Instead you might build a simple CF page that generates static CSS pages (using CFFILE) - this page could be run on a schedule (for example) to build a new static CSS page every, say, hour. You have to look at what you're doing and decide if you need really dynamic information or just sorta dynamic information. Jim Davis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:5:148091 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/5 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:5 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
