|
||
class RHTTPMessage;
An abstract HTTP message. In RFC2616, an HTTP message is defined as having a header and an optional body. This class is specialised for HTTP requests and responses.
Defined in RHTTPMessage
:
Body()const
Gets the body. The body is supplied as a MHTTPDataSupplier, which can be used to...GetHeaderCollection()
Returns the header collection for the message HasBody()const
Determine whether this message has any associated body data. RHTTPMessage()
Default (uninitialised) constructor. RemoveBody()
Removes the body SetBody(MHTTPDataSupplier &)
Sets the messages body, replacing any existing body. The body is supplied as a M...iImplementation
IMPORT_C RHTTPHeaders GetHeaderCollection();
Returns the header collection for the message
|
IMPORT_C void SetBody(MHTTPDataSupplier &aBody);
Sets the messages body, replacing any existing body. The body is supplied as a MHTTPDataSupplier
, which will then return the data in 1 or more chunks on request.
|
IMPORT_C TBool HasBody() const;
Determine whether this message has any associated body data.
|
IMPORT_C MHTTPDataSupplier* Body() const;
Gets the body. The body is supplied as a MHTTPDataSupplier
, which can be used to return the current data chunk, and to acknowledge when that chunk has been consumed by the client.
Note that the client can assume the body object will remain unchanged from when it receives the first data until the end of the transaction.
|
protected: CMessage * iImplementation;