Yes, I agree with Roland. This could make sense assuming the server side complies with this behaviour. As Roland mentioned this is not possible using HttpClient 3.0, but may be possible in the future.
Mike On 1/31/06, Roland Weber <[EMAIL PROTECTED]> wrote: > Hi Roger, > > > 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 ? > > Yes, that makes sense. At least if the server starts generating the > response before it has read the request body completely. But I'm afraid > that currently HttpClient is not going to check for the response until > it is finished with sending the request. > The asynchronous communication for 4.0 would make such an approach > possible, but we've only just started working on it. I can't see a > solution for your problem coming anytime soon. I'll remember your > scenario as a use case to consider, if that is a consolation to you :-) > > sorry, > Roland > > --------------------------------------------------------------------- > 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]
