On Wed, 2010-05-26 at 05:21 -0700, franck.mosse wrote:
> 
> 
> olegk wrote:
> > 
> > 
> >> Hi olekg,
> >> 
> >> Using a  buffer content in memory will not be a good solution for me as i
> >> have to transfert large amount of data like videos and i don't want to
> >> load
> >> the full video in memory.
> >> 
> >> Is it planned to include the support of multipart messages and stream
> >> body
> >> in the httpcore nio package ?
> >> Franck.
> > 
> > HttpCore NIO fully supports content streaming. There are presently no
> > plans to develop multipart library based on NIO.
> > 
> > Oleg
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> > 
> > 
> > 
> 
> May be i am missing something in the api because i am a newbie on nio.
> Can you tell me where to find an example showing the streaming of large
> amount of data using the http nio ?

http://hc.apache.org/httpcomponents-core-4.0.1/tutorial/html/nio.html#d0e1632


> In fact to be more clear on my need, i would like to send a multipart
> message made of some string body and an input stream body that contains a
> video. In this case, i expected to find a NMultipartEntity in the api the
> same way as NByteArrayEntity and others...

HC is not a commercial product. It is a community driven project. The
overwhelming majority of code in the project was contributed by
individual contributors. NMultipartEntity is not there because nobody
contributed it. 

> May be there is an other way to do that but i don't know... Do you have any
> sample on that ?

I already mentioned blocking I/O compatibility protocol handlers in my
previous message. While content buffering would not be a good idea in
your case, you could still use throttling protocol handler described
here:

http://hc.apache.org/httpcomponents-core-4.0.1/tutorial/html/nio.html#d0e2107 

Oleg


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to