-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Flexible request body parser #434
base: master
Are you sure you want to change the base?
Flexible request body parser #434
Conversation
- It's 100% compatible with older versions. - User can add any body parser by himself. - HTTP::MultiPartParser & URL::Encode is faster than HTTP::Body.
- Remove backward compatible layer for HTTP::Body.
use strict; | ||
use warnings; | ||
use utf8; | ||
use 5.010_001; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you really need these?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops. My vim snippet injected this. I removed this at 4a80f4e.
I saw http://search.cpan.org/~kazeburo/HTTP-Entity-Parser-0.12/lib/HTTP/Entity/Parser.pm and would love to replace HTTP::Body with a faster implementation like this. Is it still viable to update and merge this? cc @kazeburo See also: @chansen's URL::Encode::XS, HTTP::MessageParser and HTTP::MultipartParser. cc @avar |
Duh, I completely forgot this PR and re-implemented everything with #537 |
No description provided.