Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 10770 invoked from network); 29 Apr 2006 02:48:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 Apr 2006 02:48:52 -0000 Received: (qmail 47242 invoked by uid 500); 29 Apr 2006 02:48:50 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 46977 invoked by uid 500); 29 Apr 2006 02:48:49 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 46960 invoked by uid 99); 29 Apr 2006 02:48:49 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Apr 2006 19:48:49 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of mfncooper@gmail.com designates 64.233.166.179 as permitted sender) Received: from [64.233.166.179] (HELO pproxy.gmail.com) (64.233.166.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Apr 2006 19:48:48 -0700 Received: by pproxy.gmail.com with SMTP id t32so2371388pyc for ; Fri, 28 Apr 2006 19:48:27 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=eIP8+dVpHEXwLSN6VYXjAiUplDvdrQJXERZoqvm9Ej1IGfWmk0Bn+O5dVstLXUgZx4x306P9u/8iT1CCmvieYSREdyAfCvtostW0/T3k8Mq4q6roVHRbwApkoZPXB7fcAUtiPpy2LDa3WfQ2Pin36S2rEe6933O9DQravYQqS8Q= Received: by 10.35.99.14 with SMTP id b14mr3164554pym; Fri, 28 Apr 2006 19:48:27 -0700 (PDT) Received: by 10.35.100.2 with HTTP; Fri, 28 Apr 2006 19:48:27 -0700 (PDT) Message-ID: <16d6c6200604281948j210484d6t439c3f8d0ec93f89@mail.gmail.com> Date: Fri, 28 Apr 2006 19:48:27 -0700 From: "Martin Cooper" Sender: mfncooper@gmail.com To: "Jakarta Commons Developers List" Subject: Re: Current Status of Commons FileUpload In-Reply-To: <31cc37360604271201o6d84bbacma692858cd6992cfc@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_18758_31307488.1146278907762" References: <1146074634.2453.37.camel@localhost> <31cc37360604271201o6d84bbacma692858cd6992cfc@mail.gmail.com> X-Google-Sender-Auth: aa320a00b1b0dd24 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_18758_31307488.1146278907762 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 4/27/06, Henri Yandell wrote: > > On 4/26/06, Jeffrey Zellman wrote: > > Hi, > > > > I was wondering when the next release/beta will be for Commmons > > FileUpload. > > Afaik, and it's from being a user not a developer of fileupload, the > conversation has turned to a FileUpload 2.0 - in which the major issue > I've seen discussed is changing things so that the handling of > errors/overly large files is not so arbitrary. Right. There are a number of issues to tackle for 2.0. I really need to write something up on the wiki so that there's a roadmap that's not just inside my head. ;-) -- Martin Cooper Hen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > > ------=_Part_18758_31307488.1146278907762--