Quoth ludovicostev...@free.fr (Ludovico Stevens): > > I have recently registered on PAUSE and have a module to upload to CPAN; > I need some advice on the Name Space to use. > > I work with Ethernet switches & routers and I use Perl scripts to > automate tasks via the CLI (Command Line Interface). > Typically, the CLI of a switch/router can be accessed via any of Telnet, > SSH, or Serial console port. > > For many years I used Net::Telnet, but more and more customers now use > SSH instead. > Typically a switch/router will only implement CLI over SSH in an > interactive shell, and Net::SSH2 has no capabilities to handle an > interactive shell like Net::Telnet does. > > So I created my own module which presents a single consistent API and > can run over Telnet (using Net::Telnet), SSH (using Net::SSH2) or Serial > Coms port (using either Win32::SerialPort or Device::SerialPort); it > also provides all the necessary methods to deal with an interactive > shell regardless of the underlying connection type. > So if I make a script to automate a task, that script can easily work > across any of Telnet, SSH, or Serial access. > > I have written a general module, which can be used against any device > from any vendor and can be re-used to customize the functionality for > specific product families; right now I have named it: > > Net::CLI
I think I would call this Net::Tty, or perhaps Net::Terminal. 'CLI' is not what I would look for here. > Since I work with Avaya Data (ex Nortel Enterprise) switches/routers I > also have a customized version which inherits and enhances the Net::CLI > functionality just for these products; right now named: > > Net::CLI::AvayaData It's not clear from your summary below how this differs from the vanilla Net::CLI module, but I think the usual name for something like this would be Control::AvayaData. Ben
