Hi Karl,For the site in question, I ended up deciding to load the JS (minified, of course) on just the page it is required on, but I was never really happy with the performance (since a page that was designed to be flashy and impressive ends up being delayed by the download of libraries). I always sort of wondered whether a user expects to wait at the initial load and never after that point, or whether, like a developer, they expect each page to have an individual load requirement. In the era of site-wide CSS, most other pages load almost instantly (even on the slow server), so (maybe just to me) it's a really obvious discrepancy for that page only.
YSLOW is actually what led me to thinking about the HTTP requests involved on that page, and how they affect the user. I've been a big fan of that plugin since it was released.
I had never heard of Protoculous! Thanks for that! I've been using PHP minify (http://code.google.com/p/minify/) lately which doesn't like script.aculo.us too much, but does a good job of integrating all JS and CSS into a single HTTP request.
Thanks for your input! Kit ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
smime.p7s
Description: S/MIME cryptographic signature
