Skip Menu |

This queue is for tickets about the Zenoss-API CPAN distribution.

Report information
The Basics
Id: 63670
Status: rejected
Priority: 0/
Queue: Zenoss-API
People
Owner: patricksbaker [...] gmail.com
Requestors: blue [...] thisisnotmyrealemail.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Mon Dec 06 11:17:41 2010 blue [...] thisisnotmyrealemail.com - Ticket created
Subject: Please rename this to WebService::Zenoss
This is consuming a webservice, so it should be under the WebService namespace. If it was communicating directly to Zenoss using a proprietary protocol, Zenoss would make sense. And API is almost always redendant. Please see: http://pause.perl.org/pause/query?ACTION=pause_namingmodules
  Mon Dec 06 11:47:09 2010 patricksbaker [...] gmail.com - Correspondence added
On Mon Dec 06 11:17:41 2010, blue wrote: Show quoted text
> This is consuming a webservice, so it should be under the WebService > namespace. If it was communicating directly to Zenoss using a > proprietary protocol, Zenoss would make sense. And API is almost always > redendant. > > Please see: > http://pause.perl.org/pause/query?ACTION=pause_namingmodules
Hi, Thanks for the suggestion. I would prefer to keep all things Zenoss under Zenoss:: as I plan to release other modules that interact with it; not directly by API however. With that said, I'm certainly willing to redact ::API and change it to something or just use Zenoss. I believe other modules follow this paradigm, such as asterisk and nagios. Thanks, Patrick
  Mon Dec 06 11:47:09 2010 The RT System itself - Status changed from 'new' to 'open'
  Mon Dec 06 11:47:36 2010 patricksbaker [...] gmail.com - Taken
  Mon Dec 06 13:59:37 2010 patricksbaker [...] gmail.com - Status changed from 'open' to 'rejected'