Response Object Implementation (Windows CE 5.0)
The Response object returns the values that the server processed to the client browser in response to an HTTP request. The following table lists the levels of support for the Response object.
| Response method or property | Windows CE implementation |
|---|---|
| Buffer | (Property) Fully supported (see Notes). |
| CacheControl | Not supported. Use AddHeader with name ="Cache-control". |
| Charset | Fully supported. |
| Cookies | See Collection Objects. |
| ContentType | Fully supported. |
| Expires | Fully supported. |
| ExpiresAbsolute | Fully supported. |
| IsClientConnected | Not supported. |
| PICS | Not supported. Use AddHeader with name = "PICS". |
| Status | Fully supported. |
| AddHeader | Fully supported. |
| AppendToLog | Fully supported. |
| BinaryWrite | Fully supported. |
| Clear | Fully supported (see Note). |
| End | Fully supported (see Note). |
| Flush | Fully supported (see Note). |
| Redirect | Fully supported (see Note). |
| Write | Fully supported. |
Note The Buffer property indicates whether to buffer page output. When page output is buffered, the server does not send a response to the client browser until all of the server scripts on the current page have been processed or until the Flush or End method has been called.
If the current .asp file has buffering set to TRUE and does not call the Flush method, the server honors keep-alive requests that are made by the client browser. Avoiding the call to the Flush method saves time because the server does not have to create a new connection for each client browser request.
If buffering is turned off, calls to the Clear, End, Flush, or Redirect method fail, just as they do with IIS. When buffering is off, response headers must be added at the very top of the ASP page, before any text is sent to the client browser.
Windows CE does not support some of the advanced header-management functions that are available on IIS, such as CacheControl. To set one of these values, call the Response.AddHeader method with the name and value, as shown in the following code example.
<% Response.CacheControl = "private" %>
For example, the preceding example can be implemented with the following call.
<% Response.AddHeader("Cache-control","private") %>
If an advanced header-management function such as Response.CacheControl is called repeatedly on IIS-based ASP, only the value that was set in the last call to the method is sent to the client browser. On Windows CE–based ASP, calls to the Response.AddHeader method append data to the end of the headers and do not overwrite any of the existing headers of the same name.
See Also
Collection Objects | Server Objects
Send Feedback on this topic to the authors