[p2pu-dev] attachments/uploads?

[James Tatum]

+1 for S3 (although it's not a CDN :)

Linodes are great but the disk resources are their biggest weakness. One thing that will be tricky about the proposed solution is development. We'll have to work our backing store model so that devs can use either local storage or S3 for development. 

I see there is at least one library that does this kind of abstraction. django-filetransfers (which does async S3, that's important). With that it seems we'll be able to pick a storage engine in settings.py, which would rock.


On May 31, 2011, at 8:15 PM, John Britton wrote:

> Once we start accepting uploads we'll have to deal with limitations (size, filetype, etc) because hosting the files might prove to be technically challenging (bandwidth, storage). One possible solution would be to use a CDN (like Amazon S3) for uploaded files.
> --
> contact info:
> http://www.johndbritton.com
> @johndbritton - http://twitter.com/johndbritton
> 
> 
> On Tue, May 31, 2011 at 3:12 PM, Jessy Kate Schingler <jessy at jessykate.com> wrote:
> hey guys, 
> 
> what's the current thinking on the dev timeline for supporting uploads or attachments? this seems useful not just as an option for participants to host stuff, but also important for re-usability of courses. right now i can point to a url but not attach. 
> 
> thoughts?
> 
> Jessy
> --
> http://jessykate.com
> 
> 
> _______________________________________________
> p2pu-dev mailing list
> p2pu-dev at lists.p2pu.org
> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
> 
> 
> _______________________________________________
> p2pu-dev mailing list
> p2pu-dev at lists.p2pu.org
> http://lists.p2pu.org/mailman/listinfo/p2pu-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20110531/e66e4590/attachment.html>