#9115: Check for presence of os.unlink in temp.py
-------------------------------------+--------------------------------------
Reporter: michaelhart | Owner: nobody
Status: new | Milestone:
Component: Core framework | Version: SVN
Resolution: | Keywords: temp.py windows os.unlink
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by mtredinnick):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I don't think this is really the solution, since Guido's point is really
the root cause.
It sounds like we need a setting for the file-size management that says
"never, ever save to disk" and then if you've set that and somebody
uploads something that eats all your memory, that's your problem. Either
we can write to disk (in which case `os.unlink` has to exist so we can
manage the files properly) or we can't, in which case we should allow the
user to specify that. Transparently moving into that "don't write to disk
mode" would be dangerous, however, since it really does run the risk of a
small denial of service style attack so the person setting up the
applications must agree to that explicitly.
--
Ticket URL: <http://code.djangoproject.com/ticket/9115#comment:1>
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 [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
-~----------~----~----~----~------~----~------~--~---
