Hi Mike,
Many thanks for your response
Your guess is correct. The response is not available, at least not
using HttpClient, until the request has been sent. In general this
seems like a strange thing to want to do. Is there a particular use
case you had in mind?
I want to 'stream' a big payload via HTTP POST to a server, using
chunked encoding, and then receive a big payload back in the response
(again using chunked). I want the client to start processing this
response ASAP, otherwise, I guess, there will be very full buffers
somewhere ...
Does that make sense ?
Roger
Mike
On 1/31/06, Roger Menday <[EMAIL PROTECTED]> wrote:
Hi,
I am using httpclient productively, but I have a question which I hope
isn't too daft.
I would like to make a POST, and then start reading the response (in a
separate thread) before the entire request has been sent,
getResponseAsStream() appears to be non-null only when the whole request
has been sent.
My wishes are probably somewhat contrary to what HTTP intends to be I
think ...
But ..
Thanks for any help,
Roger
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
