Why not just use the backend feature that already exists? I have an S3 backend that does this...
It checks if it's on S3, if not it serves it locally. If it's on S3 it throws the url into memcache, and bob is your uncle. On Wed, Apr 14, 2010 at 9:27 AM, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > On Wed, Apr 14, 2010 at 8:58 PM, Ed Menendez <edmenen...@gmail.com> wrote: >> Agree on avoiding additional setting. >> >> Re: cache >> Basically if the file is not found locally then it goes out to the URL >> to get it. So a local file couldn't be overwritten as that's the first >> thing it checks. Cache is currently an option to the view too. Which >> should be documented so it can be turned off if disk space is limited >> locally. > > Ok. We can work through details once we're in the new feature > discussion phase for 1.3. > >> Re: 1.2 >> No problem. Should I not even open a ticket with the patch until after >> or is it OK to do now? > > Feel free to open a ticket now, just don't put it on the 1.2 milestone. > > Yours, > Russ Magee %-) > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
