Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient User Discussion" <httpclient-users@hc.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <111817.17360.qm@web23006.mail.ird.yahoo.com>
Date: Wed, 18 Feb 2009 10:58:49 +0000 (GMT)
From: Florent Georges <lists@fgeorges.org>
Reply-To: lists@fgeorges.org
Subject: Re: Writing the content of an entity
To: HttpClient User Discussion <httpclient-users@hc.apache.org>
In-Reply-To: <91ae21990902172119r54b4ebbdke9e4932b09eb9f44@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Subhash Chandran wrote:

  Hi,

  Thanks for your response.

> AFAIK, HttpEntity InputStream takes your InputStream and
> writes to request body. Only thing is, you don't deal with the
> process of looping through your InputStream and writing to
> OutputStream (as u would do in HttpURLConnection).

> In short, the InputStream method does push the content, not
> pull it as u had assumed.

  I am not sure to follow...  Are you saying that because the
implementation of InputStreamEntity, at some point, writes to an
output stream, then the interface is a push interface instead of
a pull interface?  Frankly, that sounds quite weird to me, but I
have maybe missed something.

  But the point is not rhetorical, and the goal is to be able to
avoid to bufferize the output of the subsystem that actually
generates the entity content (to an output stream,) what would
be required only to give an InputStream, or a String as content.

  Regards,

--=20
Florent Georges
http://www.fgeorges.org/


=0A=0A=0A      

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org