Hi, When I debugged into source code of Wink Client, I saw that multipart wouldn't be reading and sending like a way that you and I expected. From my view, writing a custom handler doesn't make sense in this case because the custom handler is called to write the content that you want to send (which could be any type of object) to buffered memory before being sent.
Thanks, Cuong Serafin Sedano wrote: > > I thought it would be reading and sending with the 100 http code. > > What about writing a custom handler? > > Regards. > > Serafín. > > 2011/7/26 hoangcuongit <[email protected]> > >> It still got the same problem because Wink Client also buffers whole the >> content of multipart before sending. >> >> Thanks, >> >> Cuong >> Serafin Sedano wrote: >> > >> > >> > What about send it as a multipart? >> > >> > 2011/7/25 hoangcuongit <[email protected]> >> > >> >> Hi, >> >> >> >> I knew that I didn't have space enough for the JVM memory because Wink >> >> Client does try to buffer whole the content of file to JVM memory >> before >> >> sending it to Wink Server. I can adjust the JVM memory settings to >> bear >> >> with >> >> this. But what happens if I want to send a file that's really huge >> (for >> >> instance 4Gb or 8Gb), I'm therefore looking for an alternative way. >> >> >> >> Thanks for your reply, >> >> >> >> Cuong. >> >> >> >> >> >> >> >> -- >> >> View this message in context: >> >> >> http://apache-wink-users.3471013.n2.nabble.com/Upload-a-huge-file-more-than-2Gb-tp6609909p6617759.html >> >> Sent from the Apache Wink Users mailing list archive at Nabble.com. >> >> >> > >> >> >> -- >> View this message in context: >> http://apache-wink-users.3471013.n2.nabble.com/Upload-a-huge-file-more-than-2Gb-tp6609909p6621282.html >> Sent from the Apache Wink Users mailing list archive at Nabble.com. >> > -- View this message in context: http://apache-wink-users.3471013.n2.nabble.com/Upload-a-huge-file-more-than-2Gb-tp6609909p6621674.html Sent from the Apache Wink Users mailing list archive at Nabble.com.
