Chunked is a transfer-encoding not content. It means there is no
content-length in the response header and the client simply gets the (size
of) each packet separately and then cuts the connection when the server
Francois, any idea? Chunked encoding is a *must* for http/1.1 compatibility.
----- Original Message -----
From: "Angus Robertson - Magenta Systems Ltd" <[EMAIL PROTECTED]>
Sent: Saturday, December 03, 2005 3:59 PM
Subject: Re: [twsocket] Chunked encoding with THttpCli
>> Does THttpCli support chunked encoding? If so, how do we indicate we
>> can accept it from server?
> No. If such an encoding actually exists, the latest client beta
> supports content coding 'plugins', so you can write a new unit based on
> the current GZIP coding version, and simply add it to the project, so it
> will be automatically used by THttpCli and the Accept-Encoding: header
> added to requests with whatever code is used for 'chunked'.
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://www.elists.org/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be