>> Responses Inline. I had emailed Brian directly before, figured I should send this email to the list.
On Sun, Dec 5, 2010 at 5:53 PM, brian d foy <brian.d....@gmail.com> wrote: > [[ This message was both posted and mailed: see > the "To," "Cc," and "Newsgroups" headers for details. ]] > > In article <201012031927.ob3jrvsx003...@pause.fiz-chemie.de>, Perl > Authors Upload Server <upl...@pause.perl.org> wrote: > > > The following module was proposed for inclusion in the Module List: > > > > modid: Zenoss::API > > DSLIP: bdpO2 > > description: PERL OO interface to the Zenoss API > > userid: PATBAKER (Patrick Baker) > > > Zenoss is an OpenSource monitoring system which is growing in > > popularity. In order to support the PERL users that use Zenoss, I've > > does it support Perl users too? :) > >> Well, they're a Python shop, but they do have some perlish type things. The API however allows it to be programmatically agnostic. > > > Zenoss::API was chosen as I did not want to consume a top level > > name space in the event others decide to develop PERL modules > > You don't ever take over everything under a namespace your register. > You just get the actual names, regardless of hierarchy, that you > reigister. That is, you can register Zenoss, and someone else can > register Zenoss::Foo without ever having to interact with you. > > I think Zenoss would be a better name for it. > >> One quick question. If the Zenoss namespace is registered by myself, am I still able to call my package Zenoss::API? IE currently my package is instantiated by 'my $api = Zenoss::API->connect();'. I dont know if it would make sense to have it instantiated via Zenoss->connect(); - or maybe I'm misunderstanding the namespace registration process. If you think just 'Zenoss' would be better I would just need to re-work some things, no big deal. I've uploaded my current work to PAUSE, so you can take a look there if I'm not explaining it correctly. https://pause.perl.org/pub/PAUSE/authors/id/P/PA/PATBAKER/Zenoss-API-1.0.tgz
