Ruby on Rails

On Mar 27, 11:56 am, Ahmy Yulrizka <ahmy...@gmail.com> wrote:
> I always got scared when my client ask for upload functionality. Basically
> from what I've read that when user uploaded a file it will an instance of
> the web server. So if i have one dyno (instance) on heroku, while one user
> is uploading a big file then the application would not respond to another
> user request until the file is done ?
>

Exactly when the file upload gets handed over to rails will depend on
your precise setup. On a standard apache/passenger type setup the
request only gets passed into rails when the request has been fully
received. I've not used heroku for this sort of stuff - it should be
say enough to determine what exactly happens.

> I also find a couple of solution like carrierwave-direct which the file is
> uploaded directly to the storage server (let say S3), then rails can latter
> process the file. If we are to build like a social networking which
> involves many user uploading file in the same time, what is the correct
> approach to the problem?

S3 does indeed support pre-authenticated uploads. I'd certainly
investigate this, since with heroku you're going to have to upload the
file to s3 (or similar) at some point anyway, seems like you might as
well send it straight there.

Fred
>
> Ahmy Y

--
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 rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.