Under IIS 4.0, buffering is disabled by default. This means
that your
ASP page is streamed out to the browser as it's processed. This often
gives the illusion of a more responsive page, as a certain amount of
the page can be rendered while time-consuming processes, such as
database calls, are performed; however, the downside is that you can't
redirect to another page once the HTTP headers have been sent to the
browser. This happens immediately, the first time you call
response.write or certain other methods.
Under IIS 5.0, we have the opposite situation: buffering is enabled by
default. This means that the entire ASP page is processed and
interpreted before anything is sent to the browser. Consequently, you
can redirect as often as you like, but users may get to stare at a
blank browser window while your database queries or other time-
consuming script executes.
Both choices are valid in certain circumstances. You can take the
driver's seat by deciding for yourself on a page-by-page basis
which to use. The buffer property of the response object allows
you to exercise programmatic control over this. Simply setResponse.Buffer = True
to turn buffering on, or set the property to false to turn it off.
Experiment to decide which is appropriate for your needs.
To buffer or not to buffer
By ElementK Journals, published on 14 Jul 2001
| Filed in
You might also like...
IIS forum discussion
-
Problem viewing IIS website locally
by ep1 (0 replies)
-
How to fix Mozilla thunderbird password recovery?
by ajexmartin (0 replies)
-
Invitation to take part in an academic research study
by researchlab (0 replies)
-
How to insert & edit unique value using store procedure
by umeshdaiya (0 replies)
-
How to troubleshoot Epson laser printer?
by daisywyatt618 (0 replies)
IIS podcasts
-
Hanselminutes: Startup Series: Buying an Existing Small Company or Online Application
Published 8 years ago, running time 0h34m
Scott talks to Rob Walling about how he purchases small niche products and companies online and revitalizes them. He recently purchased an existing product that consisted of a 300 gig database and tens of thousands of lines of Classic ASP. How did he know it was valuable? What's next?
Comments