From adffaces-user-return-2716-apmail-incubator-adffaces-user-archive=incubator.apache.org@incubator.apache.org Thu Apr 12 20:58:39 2007 Return-Path: Delivered-To: apmail-incubator-adffaces-user-archive@locus.apache.org Received: (qmail 37329 invoked from network); 12 Apr 2007 20:58:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Apr 2007 20:58:37 -0000 Received: (qmail 49539 invoked by uid 500); 12 Apr 2007 20:58:41 -0000 Delivered-To: apmail-incubator-adffaces-user-archive@incubator.apache.org Received: (qmail 49477 invoked by uid 500); 12 Apr 2007 20:58:40 -0000 Mailing-List: contact adffaces-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: adffaces-user@incubator.apache.org Delivered-To: mailing list adffaces-user@incubator.apache.org Received: (qmail 49440 invoked by uid 99); 12 Apr 2007 20:58:40 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Apr 2007 13:58:40 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [208.30.140.160] (HELO moroha.quovadx.com) (208.30.140.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Apr 2007 13:58:33 -0700 Received: from qxvcexch01.ad.quovadx.com ([192.168.170.59]) by moroha.quovadx.com (8.13.6/8.13.6) with ESMTP id l3CKvZlY011444 for ; Thu, 12 Apr 2007 20:57:36 GMT X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C77D45.4D696970" Subject: Limits of file upload Date: Thu, 12 Apr 2007 14:58:41 -0600 Message-ID: <820E9D2DE5261D45B6D5E9BFF0984C66014350FB@qxvcexch01.ad.quovadx.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Limits of file upload Thread-Index: Acd9RVlpsIhFyYANQ7+ovKhRO3VMQg== From: "Daniel Hannum" To: X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C77D45.4D696970 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have an application where we upload rather large (ok, VERY large) files via a file upload component. I know that I can control the size through the UPLOAD_MAX_DISK_SPACE conf parameter. =20 My question is are there any practical limits to this component. Our old application allowed up to 150 megs in an upload. They would like to up that. Speed and disk space are not an issue. I know that at some point I'd worry about the filesystem limits on file size and it's also possible that the app may timeout during the upload in extreme cases. =20 Has anyone tried these kinds of extreme cases? Should I stick with 150MB or do you think I could try 1GB. More than 1GB is certainly pushing it, I think. =20 I realize that FTP is probably a better medium for this. That's probably the future, but in the short term, we have big files that need to get here somehow. Any advice is appreciated. =20 Thanks Dan ------_=_NextPart_001_01C77D45.4D696970--