#12502: Diagram doesn't match text in Middleware documentation
-------------------------------------+-------------------------------------
Reporter: petrilli | Owner: Aymeric
Type: Bug | Augustin <aymeric.augustin@…>
Component: Documentation | Status: closed
Severity: Normal | Version: master
Keywords: | Resolution: fixed
Has patch: 1 | Triage Stage: Accepted
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 1
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by aaugustin):
Replying to [comment:18 shai]:
> I agree that the second version is better, but I still think it doesn't
achieve the goals you set for it in comment:16.
Sorry, I committed before seeing your comment. I wanted to get it done
tonight rather than let it linger for another three years :)
> Question: is it -- as implied by the suggested diagrams -- that an
exception middleware can return a template response to be processed by the
template-response middleware?
Yes, this is possible (look at `django.core.handlers.base`).
There are four possibilities for the response phase:
- exception => template_response => response
- exception => response
- template_response => response
- response
The dashes on the diagram mean that exception and template_response are
optional, so these four possibilities are represented.
--
Ticket URL: <https://code.djangoproject.com/ticket/12502#comment:20>
Django <https://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-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
