Return-Path: <becke@u.washington.edu>
Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org;
 run by ezmlm
Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org
Received: (qmail 99854 invoked from network); 1 Sep 2003 18:10:03 -0000
Received: from unknown (HELO mxout3.cac.washington.edu) (140.142.32.166)
  by daedalus.apache.org with SMTP; 1 Sep 2003 18:10:03 -0000
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout3.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id
 h81HUGq4022422
	for <commons-httpclient-dev@jakarta.apache.org>;
 Mon, 1 Sep 2003 10:30:16 -0700
Received: from u.washington.edu
 (adsl-151-203-48-229.bostma.adsl.bellatlantic.net [151.203.48.229] (may be
 forged))
	(authenticated bits=0)
	by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id
 h81HUE49014401
	(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT)
	for <commons-httpclient-dev@jakarta.apache.org>;
 Mon, 1 Sep 2003 10:30:15 -0700
Date: Mon, 1 Sep 2003 13:30:13 -0400
Subject: Re: Servlet to handle fileupload example - missing
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Michael Becke <becke@u.washington.edu>
To: "Commons HttpClient Project" <commons-httpclient-dev@jakarta.apache.org>
Content-Transfer-Encoding: 7bit
In-Reply-To: <BB791F81.F60%adrian@intencha.com>
Message-Id: <F1F69305-DCA1-11D7-8A44-00306557E112@u.washington.edu>
X-Mailer: Apple Mail (2.552)
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Putting todos in bugzilla sounds like a good idea to me.

Mike

On Monday, September 1, 2003, at 02:08 AM, Adrian Sutton wrote:

> On 01/09/2003 4:01 PM, "Dan Tran" <danttran@hotmail.com> wrote:
>
>> Thanks Michael.  Was there any reason why HttpClient
>> does not include one?  Usually it would be a big help
>> for a newbie not to figure this out first.
>>
>> -D
>
> Hi Dan,
> HttpClient doesn't include one because it focuses on the client side 
> of HTTP
> transactions and so the server side is out of scope.  Additionally if 
> we
> were to ship FileUpload we'd have to deal with all the problems that go
> along with it such as support load and synchronizing the release 
> schedule so
> we ship a stable and up to date FileUpload.  We probably should 
> improve our
> documentation about file uploading though.  I've added it to my todo 
> list
> (that doesn't seem to be getting done lately so feel free to jump in).
>
> On a side note, I think I need to move my todo list into bugzilla 
> since it's
> become pretty big and I'm not keeping up with it.  I've added that to 
> my
> todo list too. :)  Does anyone have any objections to using bugzilla 
> in a
> more informal method like that?
>
> Regards,
>
> Adrian Sutton.
>
> ----------------------------------------------
> Intencha "tomorrow's technology today"
> Ph: 38478913 0422236329
> Suite 8/29 Oatland Crescent
> Holland Park West 4121
> Australia QLD
> www.intencha.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: 
> commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: 
> commons-httpclient-dev-help@jakarta.apache.org
>