Re: Network Device API - Package Names
[email protected] (Chase Whitener)
| Newsgroups | perl.module-authors |
|---|---|
| Message-ID | <CALoNeLv-mhpf7CYw1s_V0aFNRA9bfCWq4Z=uWUd1UEvs8j9zzg@mail.gmail.com> |
Hi Greg, For the Cisco class, it's probably best to avoid "Switch::" as the first thing that comes to mind are entirely different, e.g. Switch::Plain. There already exist a handful of Cisco-related things under Cisco::. In particular, you may want to look at Cisco::UCS and Net::Cisco::ACS (maybe you don't need to do any extra work here?). And for the other, I agree with Dan, Device:: is what I'd think of. -- Chase On Wed, Nov 16, 2016 at 8:26 PM, Dan Book <[email protected]> wrote: > I recommend using Device:: as your top-level namespace, as it's already > widely used for hardware interface libraries. You can make it more granular > under that if you wish. > > On Wed, Nov 16, 2016 at 7:45 PM, Greg Foletta <[email protected]> wrote: >> >> Hello, >> >> I'm currently writing modules to interact with the APIs of network >> devices. These include the NXAPI of Cisco Nexus switches, and the API of >> Palo Alto firewalls. >> >> I'm looking for suggestions as to where to place these within the package >> space? >> >> My first consideration has been for the top level to be the device type: >> Firewall::PaloAlto >> Switch::NXAPI >> >> What are other people's thoughts? >> >> Greg Foletta >> [email protected] >> >