There are pieces in HTTP::Tiny that are independently useful. The one I have in mind presently is the HTTP response header parsing, which I’d like to reuse in a non-blocking HTTP client I’m building on top of Net::Curl.
@chansen @xdg are you opposed in principle to splitting that part of HTTP::Tiny into a separate module? I’m happy to submit a PR if so. By virtue of HTTP::Tiny’s being in core this would effectively add a standard, lightweight HTTP header parser interface to Perl, which would seem a win for the community as a whole.
There are pieces in HTTP::Tiny that are independently useful. The one I have in mind presently is the HTTP response header parsing, which I’d like to reuse in a non-blocking HTTP client I’m building on top of Net::Curl.
@chansen @xdg are you opposed in principle to splitting that part of HTTP::Tiny into a separate module? I’m happy to submit a PR if so. By virtue of HTTP::Tiny’s being in core this would effectively add a standard, lightweight HTTP header parser interface to Perl, which would seem a win for the community as a whole.
Thank you for your consideration!