AspBufferingOn
AspBufferingOn specifies whether output from an ASP application will be buffered. If the value is set to true, all output from the application is collected in the buffer before the buffer is flushed to the client browser. With buffering on, the ASP application has to completely process the ASP script before the client browser receives any output. For this reason, applications that have buffering enabled may seem slower to users than those applications that have buffering disabled, even though the total time taken for the buffered script is less. Therefore, if buffering is turned on, you should consider using the Flush method of the ASP built-in Response object to pass the user pieces of content as the script is being processed.
If this property is set to false, output from anASP script is written to the client browser as it becomes available. If buffering is turned off, any methods that modify existing HTTP headers or generate new headers must be executed before the content body is sent to the client browser. If buffering is turned on, this restriction is unnecessary.
Attribute Name | Attribute Value |
---|---|
XML Data Type | Boolean |
WMI Data Type |
Boolean
|
ADSI Data Type | Boolean |
ABO Data Type | Boolean |
ABO Metabase identifier |
MD_ASP_BUFFERINGON
|
Attributes | INHERIT |
Default Value | true |
MetaFlagsEx | CACHE_PROPERTY_MODIFIED |
User Type | ASP_MD_UT_APP |
StartingNumber | Not applicable |
EndingNumber | 0 |
ID | 7000 |
Configurable Locations
You can configure this property at the following locations in the IIS metabase.
Metabase Path | IIS Admin Object Type |
---|---|
/LM/W3SVC/n/ROOT /LM/W3SVC/n/ROOT/virtual_directory_name |
IIsWebVirtualDir |
/LM/W3SVC/n | IIsWebServer |
/LM/W3SVC | IIsWebService |
/LM/W3SVC/n/ROOT/physical_directory_name /LM/W3SVC/n/virtual_directory_name/physical_directory_name |
IIsWebDirectory |
Code Example
For general code examples, please see Code Examples to Configure Metabase Properties