Re^2: Async HTTP(S) client

What about HTTP::Async or AnyEvent::HTTP?

Net::Async::HTTP is more popular and actively maintained than HTTP::Async. Though the requirement on 5.14 makes it less portable.

Would be much nicer if you could "publish" it Perlancar style to CPAN ;-)

Perlancar should be an anti-example of using CPAN. Our company minicpan bans any module he authors or that relies upon one of his. Instead of contributing fixes to other modules, he forks them with his "corrections". "Oh, there's a typo in your docs, I'll fork it and upload a new distribution. All better" (;-P). I think this is a case of extreme resume padding.

Comment on Re^2: Async HTTP(S) client

Replies are listed 'Best First'.
Re^3: Async HTTP(S) client by cavac (Prior) on Mar 07, 2025 at 12:35 UTC
Though the requirement on 5.14 makes it less portable. Then i suggest not using any of my modules. I tend to support only supported Perl versions so i can use fairly recent Perl features (especially sub-signatures). I'm not going to ditch all the advancements of the last decade or two, just because someone wants to run an outdated, unsupported, insecure version of Perl that hasn't been maintained since the release of Minecraft 1.0... PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP Also check out my sisters artwork and my weekly webcomics	[reply]
Re^3: Async HTTP(S) client by Anonymous Monk on Mar 06, 2025 at 06:22 UTC
Though the requirement on 5.14 makes it less portable. 5.14.0 2011-May-14 lol	[reply]