Hey Paul,
In the cloud, the mongrels serving your app may be distributed across
many different servers. If they had to check a local watch folder for
uploaded files in the background and transfer those into S3, I see a
number of potential complexities that could arise. A simple one to
think of would be filename collisions. What should the background
processing do when it turns out an asset name already exists? Well,
it could of course give everything a random unique name, but that
wouldn't be so cool for apps relying on or wanting to preserve the
name. And that's just scratching the surface, I think.
Btw, have you given attachment_fu a try with the Heroku backend a
try? I think you'll find that it gives you the ease-of-use you're
looking for. All you do is specify the backend, and you won't have
even worry about S3 at all.
/Morten
On Jun 13, 2008, at 4:04 PM, DyingToLearn wrote:
>
> This might be a naive suggestion, but what if there were a reserved
> folder, and everything that my apps saved to that folder got put into
> HerokuAssets?
>
> For example:
> RAILS_ROOT/public/assets is the reserved folder
> When my apps saves a file to RAILS_ROOT/public/assets/videos/user/
> 123.mpeg
> In the background Heroku will actually do something like
> HerokuAssets.put('videos/user/123.mpeg', whatever)
>
> So basically I can interact with those files exactly as I would if
> they were on the local system, but behind the scenes they are actually
> stored on S3.
>
> I'm not saying this out of experience. I just though it _might_ be a
> way to make things more seemless.
>
> Cheers,
> Paul
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Heroku" 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/heroku?hl=en
-~----------~----~----~----~------~----~------~--~---
