Clarification of Page and Resource Request Processing Sequence

[Robert Cramer]

Just wanting to confirm (or clarify) my understanding of the page request
and rendering cycle:

Is the following true (even if not fully detailed)?

1. IIS receives a request for a .aspx page
2. IIS forwards the request to ASP.NET
3. ASP.NET then executes the requested .aspx page (okay, the class generated
for it),
and all code in the various request-related events (init, page_load,
etc).
4. ASP.NET ultimately sends HTML markup back down to the browser.
5. ASP.NET does nothing more at this point to service the specific request
for the .aspx page.
6. The browser then receives the HTML sent by ASP.NET
7. The browser then parses the HTML and renders it in the browser.
8. AS the browser is parsing the HTML and rendering it, the browser will
then send entirely new requests to the server [perhaps other servers] in
order to retrieve linked resources, like images, css files, script
files, etc.

In consideration of items 6-8 above, then, the IIS server in question
(assuming all images, css files, etc are located on the server handling the
original request for the aspx page) will typically handle multiple requests
from a browser when a single page is requested by the browser: There would
be one request for the .aspx page, then one entirely separate/new request
for EACH linked resource (css file, image, etc) included in the HTML sent to
the browser as a result of the original .aspx page request.

Is the above basically true?

Thanks!

 

[bruce barker]

yes. generally to be server friendly, the browser will only do two
concurrent requests to the same server. script includes are different
then other links, as the parsing of the html is stopped until the script
has been downloaded and added to the dom.

-- bruce (sqlwork.com)