On Fri, 12 Jan 2001, Robert Collins wrote:
> what is Httpreply used for
> *transient data with each reply sent to a client
> *persistent data stored on disk
> *both?
>
> I'm adding a list of transfer encodings to perform on the outbound data, and I assumed that the HttpReply would be the place to list
> them... but HttpReply sits under MemObject, so it looks to me like it might be persistent - and te is hop by hop only.
>
> If httpReply is wrond should I put the list in request_t or clienthttprequest ?
HttpReply is a structure that holds "binary" versions of HTTP reply headers,
including the status line and "cached" values for date, content-length, etc.
HttpReply *MemObject->reply is "written" by the server-side, in
httpProcessReplyHeader(), and probably other places. It is "read"
by the client-side in client_side.c, and probably other places.
> What confuses me is we seem to be using a request struct to store response data?
What request struct?
Duane W.
Received on Thu Jan 11 2001 - 16:07:13 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:13:17 MST