|There's more than one way to do things|
My recent post here (summary: I asked whether there were any CPAN modules desparately in need of repair) garnered a nice response from DragonFly, who noted that "that Net::Ping is due for a bit of maintainance, or possibly a more thorough overhaul..." I've worked with Net::Ping before, and been frustrated by it myself, so I thought I'd do some research and come up with some more detailed ideas.
tye's node here was very enlightening, and provided most of the information I needed. I then proceeded to scan through the firstname.lastname@example.org archives and the comp.lang.perl.* newsgroups -- it seems that a lot of people are dissatisfied with this module, but noone appears to have made a decent attempt to fix it. So, I've collected a bunch of suggestions that I have for improvements to the module. I've collected them here for public discussion... I'll appreciate any further suggestions & comments from anyone. :)
Update: See Net::Ping::External for my first attempt at implementing suggestion #2.
Once this has been discussed, I plan on doing the Nice Thing and e-mailing the module's author regarding the proposed changes; I'll have to see what kind of response (if any) I get from him before I go too much further. At any rate, here are the suggestions:
If the "auto" protocol is implemented, in what order should the code actually attempt to ping the remote host?
Also, I have no easy access to a Windows NT box w/Perl (I've only got access to Solaris, IRIX, Linux, OpenBSD, and Win9x boxen here); if I end up going ahead with this and need an NT box to test on, would there be any monks willing to help me out? Anyone else who has a more exotic system would also be of use for testing.
Thanks in advance for any input you may have.