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 [EMAIL PROTECTED] 2003-10-31 21:50 ------- I'm not sure I understand what you're doing. Are you trying to keep everything in memory, and prevent anything from being written to disk? If so, why are you trying to use *Disk*FileUpload? You should be using a custom implementation for that. If that's not what you're trying to do, then why are you setting the in- memory threshold so high? The idea behind the disk implementation is that small fields - typically the non-file fields - will be kept in memory, while the larger ones will be written to disk. I can see that perhaps pre-allocating the threshold value could be changed to pre-allocate a smaller amount if the threshold value is high - but the point of the default implementation is that it shouldn't be high in the first place. I don't understand you're point about ByteArrayOutputStream and byte[]. Why are you trying to do random access on what is intended to be just a form field? Again, it really sounds like you need a custom implementation for whatever it is you're trying to do, rather than trying to bend the default implementation to meet your needs. That is, after all, why FileUpload is designed to be easily customised. ;-) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
