#36520: Performance Regression in parse_header_params
-------------------------------------+-------------------------------------
Reporter: David Smith | Owner: Natalia
| Bidart
Type: Bug | Status: assigned
Component: HTTP handling | Version: dev
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mike Edmunds):
Replying to [comment:26 Natalia Bidart]:
> Replying to [comment:25 Mike Edmunds]:
> > Post-6.0, perhaps there could be a collaboration with Flask's
maintainers on a high-performance, secure, maintained HTTP header parser
purpose-built for web framework needs? (Or maybe there's already one in
rust just waiting for some Python bindings?)
>
> Current Flask parsing is slower than our backported `cgi` version. Were
you envisioning a collaboration to optimize their implementation for
performance (perhaps reusing some of `cgi` bits) or to find a way to use
ours across projects under a shared agreement?
I was thinking about your comment in the Python forum that "relying on the
Python stdlib whenever possible improves maintainability, reduces
potential security risks, and benefits from broader community scrutiny."
Although generally true, it seems like that isn't the case for this
particular use. But that maybe there's an opportunity for web frameworks
with that shared need (should've included Tornado, probably others) to
create a shared, de facto standard package outside of Python stdlib.
(That said, I don't see anything wrong with Django maintaining its own
backported bits of `cgi`.)
--
Ticket URL: <https://code.djangoproject.com/ticket/36520#comment:27>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070199159d6875-fe4a7d98-dc86-4f40-ba86-9d54bb475cf8-000000%40eu-central-1.amazonses.com.
