Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 55444 invoked from network); 12 May 2003 05:36:11 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 12 May 2003 05:36:11 -0000 Received: (qmail 21409 invoked by uid 97); 12 May 2003 05:38:25 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@nagoya.betaversion.org Received: (qmail 21402 invoked from network); 12 May 2003 05:38:25 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 12 May 2003 05:38:25 -0000 Received: (qmail 55208 invoked by uid 500); 12 May 2003 05:36:09 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: 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 55197 invoked from network); 12 May 2003 05:36:09 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 12 May 2003 05:36:09 -0000 Received: (qmail 21395 invoked by uid 50); 12 May 2003 05:38:23 -0000 Date: 12 May 2003 05:38:23 -0000 Message-ID: <20030512053823.21394.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 19369] - [fileupload] write() method can be invoked only once. X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19369 [fileupload] write() method can be invoked only once. martinc@apache.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From martinc@apache.org 2003-05-12 05:38 ------- I have documented the fact that write() is only guaranteed to succeed the first time it is invoked for a given file item. This allows the implementation to use file renaming, or an equivalent, while the only restriction is that the item cannot be written more than once, which is not a likely requirement in any case. There really isn't a viable alternative to this restriction without imposing the requirement that the data always be copied by write(), which itself could impose a significant performance penalty on implementations. --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org