Thanks Oleg. Thats exactly what I decided to do :). Sebbs suggestion can work but creating a HttpEntity gives me full control in writeTo method where I can copy the buffer in OutputStream (which is actually ChunkedOutputStream). Reading the code of InputStreamEntity and EntitySerializer helped :).
On Wed, Sep 22, 2010 at 8:18 AM, Oleg Kalnichevski <[email protected]> wrote: > On Tue, 2010-09-21 at 21:27 +0100, sebb wrote: > > On 21 September 2010 20:03, nitin singh <[email protected]> wrote: > > > Thanks Sebb for replying to my question. I had already gone though that > > > example. Can you be a little more specific? > > > - As I said I need to write data from a buffer when it gets available. > > > So I need a OutputStream while the example you mention below builds > from an > > > InputStreamEntity. > > > > AIUI, you don't write to the output - HttpClient reads from the > > InputStream when it wants more data. > > > > One way to do this is to create an InputStream that reads from your > buffer. > > > > If the buffer is not ready, return 0 bytes. > > > > At end, return -1. > > > > Another way is build a custom HttpEntity that generates content > dynamically and writes it out to OutputStream instance passed to the > HttpEntity#writeOut() method without providing an implementation for the > HttpEntity#getContnent(). > > Oleg > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
