Marnen Laibow-Koser wrote:
Alan Gutierrez wrote:
Marnen Laibow-Koser wrote:
DK wrote:
Hi, I don't know if there are differing opinions on this, but seems to
me that apps that use such large files will write a file manager
(desktop based app or at least activex) that monitor or possibly
divide such files into smaller pieces.
Not necessarily Look at Dropbox (though they do use a Flash upload
tool).
Dropbox is what he is describing. The start you off by having you
install a filesystem extension.
But you don't have to. I exchange large files (hundreds of MB, not 4
GB) on Dropbox all the time, but I've never installed their desktop
software. It's only for convenience AFAIK.
I think it is the other way around. Their getting started link says
"Download". They want you to get the download software. The HTTP upload
is for convenience. I'm offering this as an opinion.
The OP wants to upload more than 4GB and I wouldn't trust HTTP to
transfer 4GB from a client to a server on a regular basis. There is no
way to resume a failed upload. If the OP is building a web application,
they are going to have to find an alternative. If they are building an
application with a web front end, maybe they can use SFTP as a file
transfer client for large files, and the web UI to manage the files once
they have been uploaded.
Basically, Qin Qin, you are right in noting that HTTP upload is only
good for reasonable sized uploads, whatever size reasonable is at the
time that you read this. (Images, documents, etc.)
--
Alan Gutierrez - [email protected] - http://twitter.com/bigeasy
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
