Tests still don't pass but 'you actually get a "not ok" instead of "Looks like you planned 4 tests but ran 3"'. Thanks, Tod McQuillin!
avenj on irc.perl.org #poe pointed out that Socket::GetAddrInfo 0.22 changed public behavior and began throwing the following error. This change compensates for that and requires version 0.22 or later. :newapi tag is no longer supported by Socket::GetAddrInfo; just 'use' it directly
Modified resolve() to return a request ID. Added cancel(), which accepts a request ID and cancels it. POE::Component::Client::Keepalive requires it.
Fixed thanks to Sergei Kozunov's bug report and test case. A sidecar process was created at startup, but no idle timeout was set. These timeouts are only set when requests happen, and in an application where all addresses are already resolved, no timeout is set. So the component lingers forever.
_poe_sidecar_closed() was destroying the wrong sidecar process. Thank you, Kozunov, for the code review and bug report. Two little octets can make a huge difference.
Dylan Doxey pointed out that Socket::GetAddrInfo rejects tainted addresses. Untaint them first, per his recommendation and test case.
Larwan Burke pointed out that localhost is a bad name to resolve when testing for IPv6 availability. It tends to be in /etc/hosts, which resolves whether or not the named can.
…ence. As IPv6 is adopted, more and more places will behave differently than expected. The POCO_RESOLVER_IPV environment variable gives users a way to override the legacy behavior during this potentially painful transition.
…agers. Applied a modified versin of a patch from Markus Jansen at Ericsson. It adds a parameter to POE::Component::Resolver so the developer can point to a custom sidecar program. That program can be bundld in PAR using special techniques. Thanks also go to Steffen Mueller and Roderich Schupp, who helped design the patch.
…ompted by Karen_m's memory issues, and recommended by gcola, Hinrik, and Apocalypse on irc.perl.org #poe. You people rock! :)
…structor parameter to override just how long that is. This is a partial response to Karen_m's report of PID and memory churn introduced by lots of forking.
…ddresses. We assume localhost can resolve.