Hi Yoav,

I posted some code to commons-dev in June which provided support (not a
complete solution, but sufficient to allow progress reporting to be
implemented on top of fileupload) for an implementation I am using.

To date, aside from promises to look at it, I have received no comment. 
I am currently working on the http request parsing in turbine and have
been considering forking the file-upload code, which originally came
from turbine into a fulcrum component to support the fulcrum request
parsing. Perfect or not (and its not), I am already using a forked
version of commons-fileupload-1.0, providing support for progress
reporting in my turbine based applications.

I would be delighted if someone would look at it.

Regards,

Peter


On Tue, 2003-12-23 at 14:44, Shapira, Yoav wrote:
> Howdy,
> Please do NOT submit a bug or even an enhancement request on a progress
> bar for FileUpload without discussing it here or on commons-user first.
> This is a significant, non-trivial, highly fraught with bugs area.  I've
> never seen a perfect implementation of this feature yet, so I'd want it
> rigorously tested before adding it (if possible at all) to fileupload.
> 
> Yoav Shapira
> Millennium ChemInformatics
> 
> 
> >-----Original Message-----
> >From: Eric Pugh [mailto:[EMAIL PROTECTED]
> >Sent: Tuesday, December 23, 2003 9:43 AM
> >To: Commons-Dev (E-mail)
> >Subject: [Fileupload] Progress Bar?
> >
> >Someone posted a long time ago a progress bar for Fileupload.  I
> checked
> >the
> >bug list[1] but didn't see it.  Could they submit a bug?
> >
> >Eric Pugh
> >
> >[1]
> >http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status
> =ASS
> >I
> >GNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1
> =1&e
> >m
> >ail2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&c
> hang
> >e
> >din=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Commons&co
> mpon
> >e
> >nt=File+Upload&short_desc=&short_desc_type=allwordssubstr&long_desc=&lo
> ng_d
> >e
> >sc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&k
> eywo
> >r
> >ds=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-
> >0=&cmdtyp
> >e=doit&order=%27Importance%27
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> This e-mail, including any attachments, is a confidential business communication, 
> and may contain information that is confidential, proprietary and/or privileged.  
> This e-mail is intended only for the individual(s) to whom it is addressed, and may 
> not be saved, copied, printed, disclosed or used by anyone else.  If you are not 
> the(an) intended recipient, please immediately delete this e-mail from your computer 
> system and notify the sender.  Thank you.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
Peter Courcoux <[EMAIL PROTECTED]>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to