#13960: abstract file upload/download handling
-------------------------------------------+--------------------------------
Reporter: wkornewald | Owner: nobody
Status: new | Milestone: 1.3
Component: File uploads/storage | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Comment (by wkornewald):
I just left the naming and other low-priority questions to the last design
step. But you're right, TransferBackend would be much better.
We can't extend the existing storage API because the storage mechanism
(e.g., file system) doesn't necessarily know anything about the upload
mechanism (e.g., streaming in-memory) and both don't know anything about
the download mechanism (e.g. X-Fileserve). These are three completely
separate things. Only in some cases they belong together (e.g., Amazon S3,
Google App Engine Blobstore, etc.).
This also means we can't use it as a transfer parameter to FileField. The
API is not limited to the storage mechanism.
The whole approach of adding project-specific details directly to the
models and app code makes Django apps less reusable. The configuration-
based approach allows the same app to be used with App Engine, S3, your
local home server, and any other hosting solution and that's the goal
behind this API: Abstracting the file transfer and storage, so reusable
apps can be written.
--
Ticket URL: <http://code.djangoproject.com/ticket/13960#comment:4>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
