Actually I think Ajax uses a different set of tubes.
On 3/17/07, Dean H. Saxe <[EMAIL PROTECTED]> wrote:
On Mar 17, 2007, at 9:53 PM, Howard Fore wrote:
> I just don't think that the number of http connections in a
> page is the final measure of that page's performance.
>
If it did, we'd never
On Mar 17, 2007, at 9:53 PM, Howard Fore wrote:
I just don't think that the number of http connections in a
page is the final measure of that page's performance.
If it did, we'd never see anyone use AJAX. AJAX apps are noisy
little things!
Thanks for confirming my suspicions on this one
Nope not ticked off. But first, "how the browser saves files" was your
issue, not mine:
it solves the problem of a user
saving the page locally just as well as using a full qualified path in the
head of the page would. "
The Yahoo study is a good read, though it seems a little "duh" to me.
("No
H No. You're wrong. Seriously, not trying to tick you
off, but you should read this:
http://yuiblog.com/blog/2006/11/28/performance-research-part-1/
I fully understand and am aware of the separation of content and
style, it's pro's and con's. How the browsers save things
One of the nice things about using style sheets that are external to your
HTML is that modern browsers won't download the CSS file again if the file
hasn't changed. So you save n KB per HTTP request. Small, but it does add
up, especially for a site with a lot of pages, like a shopping site. As far
