Hi, Markus. It would seem that PAR (and other packaging tools?) can't find the Sidecar module because I neglected to actually use it. Please see the included patch, which resolves the missing Sidecar problem for Windows and anything else that detects "use" statements in the source.
Do you ever supply a sidecar that isn't POE::Component::Resolver::Sidecar? A parameter would be excellent for a general-purpose sidecar-based module, but I think it's not so useful here. commit 638cd9e616a5b4ffbf413672784f41896de97430 Author: Rocco Caputo <[email protected]> Date: Fri Jul 29 00:44:00 2011 -0400 Load the POE::Component::Resolver::Sidecar class. The presence of this module is requested on MSWin32. Resolves rt.cpan.org ticket 69172, reported by Gabor Szabo. diff --git a/lib/POE/Component/Resolver.pm b/lib/POE/Component/Resolver.pm index ff7ec8b..6614189 100644 --- a/lib/POE/Component/Resolver.pm +++ b/lib/POE/Component/Resolver.pm @@ -9,6 +9,8 @@ use Time::HiRes qw(time); use Socket qw(unpack_sockaddr_in AF_INET AF_INET6); use Socket::GetAddrInfo qw(:newapi getnameinfo NI_NUMERICHOST NI_NUMERICSERV); +use POE::Component::Resolver::Sidecar; + use Exporter; use base 'Exporter'; our (@EXPORT_OK) = qw(AF_INET AF_INET6); -- Rocco Caputo <[email protected]> On Jul 15, 2011, at 06:17, Markus Jansen wrote: > Hi Rocco, > > based on the excellent input I got so far from you and Steffen, I have now > found a simple solution on the POE side > without any assumptions towards PAR (or whatever special system used, even > with PAR there is more than one way to do it :-). > > The idea is simply to make $sidecar_program configurable, and leave the > solution details to the application if special ones are needed. > Find a possible [tested] patch below, and please consider it for integration > in POE::Component::Resolver 0.913. > > Best regards, > > Markus
