In message <[email protected]>, Carsten Bormann writ es: > On Jun 25, 2010, at 16:16, Brian E Carpenter wrote: > > > initial phase of contact with a server > > To get the front page of the New York Times (http://www,nytimes.com), "a serv > er" a couple of minutes ago meant > > http://admin.brightcove.com/ > http://b.scorecardresearch.com/ > http://creativeby1.unicast.com/ > http://googleads.g.doubleclick.net/ > http://graphics8.nytimes.com/ > http://markets.on.nytimes.com/ > http://pagead2.googlesyndication.com/ > http://ping1.unicast.com/ > http://s0.2mdn.net/ > http://secure-us.imrworldwide.com/ > http://up.nytimes.com/ > http://wt.o.nytimes.com/ > http://www.nytimes.com/ > (I'm not sure I caught all the ones accessed from JavaScript.) > And NYTimes is not nearly the worst offender here. > > No, browser vendors won't put in a two-second wait for each of these.
If we use the .5 of a second delay then there is 1 second of delay total for this page attempting to connect through a broken IPv6 transport layer. .5 of second trying www.nytimes.com and .5 of a second for each of the others however they are all being fetched in parallel so the effective delay of all the other items combined is only .5. > Gruesse, Carsten > > _______________________________________________ > Ietf mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/ietf -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [email protected] _______________________________________________ Ietf mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf
