#12502: Diagram doesn't match text in Middleware documentation
-------------------------------+------------------------------------
Reporter: petrilli | Owner:
Type: Bug | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by 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. In particular, it doesn't
clarify the relationship between the three middleware functions on the way
out.
Here's a quick ascii-art sketch of what I think the diagram should look
like. Every block should be expanded to "middleware1, middleware2,
middleware3" in the correct order as in my previous suggestion.
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? The below represents my guess that this is
not the case.
{{{
# |
# V
# [ process_request ]
# |
# V
# [ process_view ]
# |
# V
# [ USER VIEW ]
# / | \
# [process_exception] | [process_template_response]
# \ V /
# [ process_response ]
# |
# V
}}}
(Of course, the arrows to process_exception and process_template_response
should be formed and colored to mark their optionality etc).
--
Ticket URL: <https://code.djangoproject.com/ticket/12502#comment:18>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
