#4416: HttpResponseServiceUnavailable patch
-----------------------+----------------------------------------------------
Reporter: semente | Owner: adrian
Status: new | Component: Core framework
Version: SVN | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------+----------------------------------------------------
Changes (by mtredinnick):
* needs_better_patch: => 0
* stage: Unreviewed => Design decision needed
* needs_tests: => 0
* needs_docs: => 0
Comment:
It's not clear that creating an extra class for every HTTP response code
is a good idea. It's a lot of classes and most of them are just changing
one number. Maybe HttpReponse can take a status code param or something.
We need to think about this some more.
--
Ticket URL: <http://code.djangoproject.com/ticket/4416#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
