Chris and Jesse, Thanks, both good points. For general consumption it'll probably be best to make an additional var for the inactivity timeout.
I've worked with many different telnet implementations over many years and cannot recall ever seeing another one without an inactivity timeout. I'm mystified how others have dealt with this issue in Telnet.pm, and have wondered if I'm the only one using it anymore. A posting on the perl.misc newsgroup nine months ago got no responses. I plan to move to ssh for my next release. What's up on CPAN right now for ssh seems a little preliminary. ----- Original Message ----- From: "Chris Devers" <[EMAIL PROTECTED]> To: "James Eshelman" <[EMAIL PROTECTED]> Cc: "Boston Perl Mongers" <[EMAIL PROTECTED]> Sent: Friday, February 01, 2002 12:12 PM Subject: Re: [Boston.pm] Telnet timeout On Fri, 1 Feb 2002, James Eshelman wrote: > 1. Is there a better scheme? Subclass the module with e.g. Net::Telnet::Dynamic (or something to that effect)? This avoids having to mess around with N::T, for people that depend on the current behavior. Alternatively, extend the module itself with some sort of dynamic_timeout parameter that defaults to 'off'? -- Chris Devers "Okay, Gene... so, -1 x -1 should equal what?" "A South American!" [....] "no human can understand the Timecube" and Gene responded without missing a beat "Yeah. I'm not human."
