It's not necessarily terrible if you use proper expiration headers. But I agree, better (and easier) to smash all the JS into a single static file and just use that.
On 7/11/07, Dave Watts <[EMAIL PROTECTED]> wrote: > > If I was to try and solve the problem on the other end (after > > the site was developed), I would first identify all the > > javascript objects that were in use, and where they were > > being used within the application. No idea on the best > > approach for this... Seems like a manual search. Once I had > > them all inventoried, I would build a single 'javascript.cfm' > > file that consists of conditional logic wrapped around > > javascript, where the conditions identified specific > > javascript functionality given by javascript objects. At the > > top of every page, I would put a <cfparam name="jObjects" > > default="accordian,XMLHttpRequest,autocomplete"> (where the > > default values are the objects that I want included on that page). > > > > After all of this was done, I would include the > > javascript.cfm like this: > > > > <script type="text/javascript" src="javascript.cfm"></script> > > > > Of course I don't know how well this deals with browser > > caching issues... > > That would be a terrible approach, because of browser caching issues. You'd > be much better off just having one static JS file that gets used by every > page, but only downloaded once. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > -- Barney Boisvert [EMAIL PROTECTED] http://www.barneyb.com/ Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 & Flex 2 Free Trial http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:283491 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
