From commons-user-return-10174-apmail-jakarta-commons-user-archive=jakarta.apache.org@jakarta.apache.org Tue Dec 21 15:41:24 2004 Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 91661 invoked from network); 21 Dec 2004 15:41:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 21 Dec 2004 15:41:23 -0000 Received: (qmail 12677 invoked by uid 500); 21 Dec 2004 15:40:01 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 12594 invoked by uid 500); 21 Dec 2004 15:40:00 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 12529 invoked by uid 99); 21 Dec 2004 15:39:59 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of dakota.jack@gmail.com designates 64.233.184.206 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.206) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 21 Dec 2004 07:39:55 -0800 Received: by wproxy.gmail.com with SMTP id 69so46125wri for ; Tue, 21 Dec 2004 07:39:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=UmBs4J7SZ3+m5A90I6cA19p6Z1O2Q+OMoQR/aRXTLFOoaxI8IGdekx69jB+DOrQnA4JAyB+qxHOjiD45E9sTl4PCqDf0bahidjrMXlELAGGzeKKieGhZ8AHcMASl1JhxdqhJM+OW8aamp0mGGICF7OE4XPKPJZBS0a4yrCcZLF8= Received: by 10.54.8.73 with SMTP id 73mr2943wrh; Tue, 21 Dec 2004 07:39:46 -0800 (PST) Received: by 10.54.48.44 with HTTP; Tue, 21 Dec 2004 07:39:46 -0800 (PST) Message-ID: Date: Tue, 21 Dec 2004 07:39:46 -0800 From: Dakota Jack Reply-To: Dakota Jack To: Jakarta Commons Users List Subject: Re: [FileUpload] Testing for existence of file In-Reply-To: <006601c4e6f7$1012e1c0$0d02a8c0@athlon> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <006601c4e6f7$1012e1c0$0d02a8c0@athlon> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Lo, Rhino, One thing you have to do is to integrate whatever you do here with what you do about uploading empty files. As long as your policies on the two are consistent and integrated, I don't see a big problem. If you accept empty files, then you might have to inform your client that the file was empty and that this can be so for a number of reasons (including a non-existent file) which you might want to list with choices to the client on what to do. You might also want to take care of this on the client end, leaving the server side ignorant of whatever choices the client happens to be making. Jack -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ "You can't wake a person who is pretending to be asleep." ~Native Proverb~ "Each man is good in His sight. It is not necessary for eagles to be crows." ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ ----------------------------------------------- "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org