Opened 8 years ago
Closed 8 years ago
#26452 closed Cleanup/optimization (fixed)
Load middleware on server start rather than on first request
| Reported by: | David Evans | Owned by: | nobody |
|---|---|---|---|
| Component: | HTTP handling | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description
This was discussed in more detail on django-dev but, briefly, the reasons for needing lazily initialization of middleware on first request no longer hold and it makes more sense to do this on application start up.
The suggestion got +1s from at least two core devs (Aymeric and Florian).
Proposed patch to follow imminently.
Change History (3)
comment:1 by , 8 years ago
| Has patch: | set |
|---|
comment:2 by , 8 years ago
| Component: | Core (Other) → HTTP handling |
|---|---|
| Patch needs improvement: | set |
| Summary: | Remove lazy initialization of middleware → Load middleware on server start rather than on first request |
| Triage Stage: | Unreviewed → Accepted |
| Version: | 1.9 → master |
Note:
See TracTickets
for help on using tickets.
Left a few comments for improvement on the PR.