commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 24306] - Fileupload fails for forms with a large number of inputs
Date Fri, 31 Oct 2003 22:04:51 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24306>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24306

Fileupload fails for forms with a large number of inputs





------- Additional Comments From MikeSamuel@yahoo.com  2003-10-31 22:04 -------
The scenario I'm dealing is a form with a lot of non-form inputs, and 1 form
input that I want to process in memory when possible, but write to disk when
not.  I chose a higher in memory threshold because that seems to get the best
throughput in our situation.

My main issue with the current design is that it preallocates the in memory
threshold **even for non-file inputs**.

My point about ByteArrayOutputStream and byte[] was that since you can't do
random access on the underlying byte[] because it's private, there's no point in
using a single byte array.  It's more efficient from both a memory and processor
standpoint to stream into a linked list of byte buffers than expand a single
buffer, incurring a copy penalty.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message