HTML and ASP or ASP only? Pros and cons?

[Al Smith]

Hi,
What makes more sense? Creating a HTML document that calls ASP routines or using ASP only to create all of the HTML pages?
Are there any pros or cons to either?
Thanks,
Al.

[lenin]

Preference only, I try to condense as much as possible into ASP, I think I have read that it is more effiecient to have a single block of ASP as opposed to fragmented blocks interspered with HTML.

Lenin

I may not be understanding the question but either a page is static HTML or it's an ASP page, it can't be both(unless you're loading an image which is a cool trick).

Meaning, an html page can request an asp page that in turn sends back dynamically generated html content. If a page is not going to change very often it's probably more efficient to build it as a static html page(no asp). If content is going to change often then build the page as an ASP page. It really depends on the content, there's no hard fast rule.

As for keeping blocks of asp together, the reason one might do this is to eliminate possible trips back to the browser which ends up being inefficient. To eliminate any unneccessary trips to the browser turn on buffering at the start of the page: Response.Buffer = True. This will buffer the output until the page is done processing or until the page hits a Response.Flush.