* UploadedFile: why mv (and never cp)?
@ 2012-04-07 6:54 wtn
2012-04-07 20:02 ` wtn
0 siblings, 1 reply; 2+ messages in thread
From: wtn @ 2012-04-07 6:54 UTC (permalink / raw
To: Rack Development
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?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: UploadedFile: why mv (and never cp)?
2012-04-07 6:54 UploadedFile: why mv (and never cp)? wtn
@ 2012-04-07 20:02 ` wtn
0 siblings, 0 replies; 2+ messages in thread
From: wtn @ 2012-04-07 20:02 UTC (permalink / raw
To: Rack Development
Pardon me, my subject line was inverted. It should have read:
"UploadedFile: why cp (and never mv)?"
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-04-07 20:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-04-07 6:54 UploadedFile: why mv (and never cp)? wtn
2012-04-07 20:02 ` wtn
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).