Re: Async HTTP(S) client

Replies are listed 'Best First'.
Re^2: Async HTTP(S) client by ikegami (Patriarch) on Mar 22, 2025 at 13:19 UTC
And there's LWP::Protocol::AnyEvent::http that allows you to keep using the familiar LWP interface. If you need async HTTP(S) requests, but don't need to be async with anything else, I recommend Net::Curl::Multi. Powerful engine, and great performance.	[reply]
Re^2: Async HTTP(S) client by Anonymous Monk on Mar 05, 2025 at 22:15 UTC
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.	[reply]
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]
Re^2: Async HTTP(S) client by cavac (Prior) on Mar 07, 2025 at 12:28 UTC
Yeah, i'm planning to eventually release it in CPAN. But first i want to test it in my own projects under real world conditions and get at least the major kinks worked out. I basically do the same with Net::Clacks. Before i release major changes that might affect the stability, it will already have been running for days or even weeks on a few live systems of mine. Since the UA is new (and hasn't been thorougly tested yet), it doesn't yet make sense to publish it on CPAN. That way, i'm free to rumble around in the internals, change the API if necessary, rewrite the whole thing from scratch if i come up with a better solution etc, without me having to worry about other people having to rewrite their code. (I'm not a pythong AI dev, i actually care about backward compatibility somewhat). 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 Intrepid (Curate) on Apr 14, 2025 at 18:06 UTC
Hwoa, pythong? I never heard that one before, I like it but a wee bit catty. I suppose in the Perl vs. Python dispute that's par for the course ;-). Apr 14, 2025 at 18:05 UTC	[reply]


Do you know where your variables are?
	PerlMonks