DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=25830>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=25830 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[EMAIL PROTECTED] ------- Additional Comments From [EMAIL PROTECTED] 2006-01-05 18:41 ------- The FileUploadProgressReporter is interesting. Another example is http://sourceforge.net/projects/megaupload - they have a commons and a struts version. Unfortunately, their void com.raditha.megaupload.MultipartIterator.writeStats(long bytesRead) writes into a file while I guess a little FileUploadProgressReporter bean would not really clutter the HttpSession too much. Also, serializability of FileUploadProgressReporter doesn't appear to be too important to me, because normally I wouldn't need such information to survive a container restart. megaupload has a good example what the corresponding jsp's could look like without requiring much javascript. Alternatively, see also http://www.onjava.com/pub/a/onjava/2003/06/11/jsp_progressbars.html . Too bad the promising expectations raised by martin cooper in http://marc.theaimsgroup.com/?l=struts-user&m=107973238105843&w=2 didn't materialize for the recent 1.1 release - I don't see any of it in the SVN HEAD :( To keep the changes even smaller and not needing a new class, how about extending org.apache.commons.fileupload.RequestContext with a public int getBytesRead(); public void setBytesRead(int bytesRead); public Date getStartTime(); public void setStartTime(Date date); after each of the two set methods, the RequestContext implementation would place itself into the session... - what do you think? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
