I think it's an API limitation. Many backends don't support last modified times, and even if they all did, it's incorrect to assume that last modified time is an accurate heuristic for whether a file has already been uploaded or not. It might be a better idea to let the backends decide when a file has been changed (instead of just calling the backend's last modified method).
Dan On Sun, Sep 30, 2012 at 2:28 PM, Stephen Burrows < stephen.r.burr...@gmail.com> wrote: > I use S3 as well, and I have seen cases where files get copied that I know > don't need to be. That being said, it was never so slow that it was an > issue for me. Is there clear evidence that this is something which can't be > handled by the S3 backend due to an inadequate API on the django side? > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-developers/-/D9eemazwQUQJ. > > To post to this group, send email to django-developers@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-developers@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.
