com.HttpServiceRequest.beginXmlResponse
Starts an HTTP streaming response.
Syntax
beginXmlResponse(
code INTEGER,
description STRING )
RETURNS xml.StaxWriter
- code defines the status code of the response.
- description defines the description of the response.
Usage
The beginXmlResponse()
method starts an HTTP streaming response by sending a
status (code) and description (description), followed by the
headers previously set, and returns a xml.StaxWriter
object ready to send XML as the
HTTP body.
code
returned ​can be a value between 100 and 999. You
can send any code in this range. This provides support for the status codes returned by HTTP,
WebDAV, other Request for Comments (RFC) codes, etc. The following determines how the
description
is handled:- If the code is recognized (as one of the standards) and the description is
NULL
, the code standard description is sent to the client. - If the code is not recognized, the description you provide is added. If you do not provide a description, a default, "No Message", is sent to the client as information about the code.
It is important for the server to return a status code, following the HTTP standards, otherwise the client may fail to interpret the response. For instance, if the request is malformed, the server is expected to send an HTTP response with the code of 400 (Bad Request).
If the request fails to be read, its content will be discarded; for example, when a request is not well formatted.
The default Content-Type header is text/xml
, but it can be changed if of the
form */xml
or */*+xml
. For example:
application/xhtml+xml
.
In HTTP 1.1, if the body size is greater than 32k, the response will be sent in several chunks of the same size.
In case of error, the method throws an exception and sets the
status
variable. Depending on the error, a human-readable description of the
problem is available in the sqlca.sqlerrm
register. See Error handling in GWS calls (status).
The int_flag variable is checked during GWS API call to handle program interruptions, for more details, see Interruption handling in GWS calls (int_flag)