UploadedFile: why mv (and never cp)?
27 views
Skip to first unread message
wtn
Apr 7, 2012, 2:54:49 AM4/7/12
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?
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?
wtn
Apr 7, 2012, 4:02:35 PM4/7/12
to Rack Development
Pardon me, my subject line was inverted. It should have read:
"UploadedFile: why cp (and never mv)?"
"UploadedFile: why cp (and never mv)?"
Reply all
Reply to author
Forward
0 new messages