From: wtn <wtnelson@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: UploadedFile: why mv (and never cp)?
Date: Fri, 6 Apr 2012 23:54:49 -0700 (PDT) [thread overview]
Message-ID: <ee51f916-fc43-4e6d-9e5b-52514995ad57@x17g2000yqj.googlegroups.com> (raw)
Rack::Multipart::UploadedFile.new uses FileUtils.copy_file.
This seems like a safe default. However, FileUtils.move is a better
option for many applications. When files are large, copying really
slows things down.
Is there interest in adding "move" behavior as an option?
next reply other threads:[~2012-04-07 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 6:54 wtn [this message]
2012-04-07 20:02 ` UploadedFile: why mv (and never cp)? wtn
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=ee51f916-fc43-4e6d-9e5b-52514995ad57@x17g2000yqj.googlegroups.com \
--to=rack-devel@googlegroups.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).