From: James Tucker <firstname.lastname@example.org> To: email@example.com Subject: Re: Not cleaning up tempfiles for multipart? Date: Mon, 8 Mar 2010 14:49:41 +0000 [thread overview] Message-ID: <42B58BD5-579C-415E-A264-7DF262717B0E@gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> [-- Attachment #1: Type: text/plain, Size: 1404 bytes --] On 8 Mar 2010, at 14:43, Charles Oliver Nutter wrote: > On Mon, Mar 8, 2010 at 5:30 AM, Hongli Lai <email@example.com> wrote: >> On Mar 8, 12:26 pm, Hongli Lai <hon...@phusion.nl> wrote: >>> Charles's middleware looks simple enough. I approve. >> >> Sorry. I mean Eric's. :) >> >> Another thing that you might want to keep in mind is that users might >> File.rename() a certain Tempfile, in which case you will not want to >> unlink it. For example suppose one uploads a large file to the web >> server, I think there are web apps out there that will simply rename() >> the tempfile to the storage directory and therefore avoid an expensive >> copy operation. > > I don't think it should be specified behavior that a tempfile *ever* > exists on disk. The mechanism of temporary storage for a large > incoming post should be a black box. Consider systems that won't > actually have a writable filesystem, like GAE; there, the "tempfile" > data would be stored in memory or in BigTable. > > Rack should not require that large multipart posts or anything else > require a filesystem, nor guarantee that they'll be on any filesystem > that exists. It's for this reason that I'd prefer to see this handled correctly by servers +/ handlers in general. Middleware may use what it likes, but it takes responsibility for cleanup of whatever it creates. > > - Charlie [-- Attachment #2: smime.p7s --] [-- Type: application/pkcs7-signature, Size: 3679 bytes --]
next prev parent reply other threads:[~2010-03-08 14:49 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-03-05 14:40 Charles Oliver Nutter 2010-03-05 14:47 ` Charles Oliver Nutter 2010-03-05 14:48 ` Charles Oliver Nutter 2010-03-06 10:20 ` Hongli Lai 2010-03-07 14:25 ` Charles Oliver Nutter 2010-03-06 7:55 ` Eric Wong 2010-03-06 10:25 ` Hongli Lai 2010-03-07 14:34 ` Charles Oliver Nutter 2010-03-08 0:22 ` Eric Wong 2010-03-08 1:12 ` Eric Wong 2010-03-17 15:41 ` Charles Oliver Nutter 2010-03-18 9:54 ` Eric Wong 2014-01-06 22:45 ` Wojtek Kruszewski 2014-02-11 21:05 ` Eric Wong 2014-03-27 21:40 ` Lenny Marks 2010-03-07 23:53 ` Eric Wong 2010-03-08 11:26 ` Hongli Lai 2010-03-08 11:30 ` Hongli Lai 2010-03-08 14:33 ` Randy Fischer 2010-03-08 14:43 ` Charles Oliver Nutter 2010-03-08 14:49 ` James Tucker [this message] 2010-03-17 2:37 ` Eric Wong 2010-03-08 13:22 ` Charles Oliver Nutter 2010-03-08 14:42 ` James Tucker 2010-03-08 17:24 ` Hongli Lai 2010-03-09 7:43 ` Charles Oliver Nutter 2010-03-08 10:05 ` James Tucker 2010-03-07 14:27 ` Charles Oliver Nutter 2010-03-08 0:18 ` Eric Wong 2010-03-08 10:07 ` James Tucker
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-list from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://groups.google.com/group/rack-devel * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=42B58BD5-579C-415E-A264-7DF262717B0E@gmail.com \ --firstname.lastname@example.org \ --subject='Re: Not cleaning up tempfiles for multipart?' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/rack.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).