#2070: Large streaming uploads
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: jacob
Status: assigned | Component: Core framework
Version: SVN | Resolution:
Keywords: streaming, upload, large | Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 1
----------------------------------------+-----------------------------------
Comment (by Michael Axiak <[EMAIL PROTECTED]>):
Replying to [comment:144 anonymous]:
> Why not skip request.FILE['video']['filename'] at all? This is provided
by request.FILE['video'] anyway.
> IMHO having filename as an separate parameter makes only sense if this
would be used somehow directly, but currently the filename/path where the
file gets saved is changed by the field (field.get_directory_name() and
field.get_filename(filename)).
Well, save_video_file() is meant to allow someone to save a file. Unless
that file is specifically provided in a post (it's not necessarily, and in
many of my applications it's not...generated images come to mind).
We *can* have it accept both sets of arguments, but then it's too
nonorthogonal. Perhaps we should just create a new one?
{{{move_video_file()}}}??
--
Ticket URL: <http://code.djangoproject.com/ticket/2070#comment:145>
Django Code <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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
