On 11/06/11 12:29, brian d foy wrote:
> [[ This message was both posted and mailed: see
>    the "To," "Cc," and "Newsgroups" headers for details. ]]
> 
> In article <201111040111.pa41b6hr019...@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:       Net::DNS::Sinkhole
>>   DSLIP:       adpOp
>>   description: A sinkholing DNS server
> 
> This sounds more like an application rather than the implementation of
> a network protocol. We have some thoughts on the use of Net::*
> 
> https://pause.perl.org/pause/authenquery?ACTION=pause_namingmodules
> 
> Maybe a good name would be simply "Sinkhole" :)
> 

I read the Naming Modules page before registering the namespace, and
shyed away from breaking new ground with a new top-level namespace.

Net::DNS::Sinkhole (alpha code, still under development on
github.com/warewolf/Net-DNS-Sinkhole) is mostly a purpose driven
customization of two Net::DNS modules, Net::DNS::Nameserver and
Net::DNS::Resolver::Programmable.

I opted to put my code under the Net::DNS namespace because those two
Net::DNS modules are what my code subclasses.  It seemed to fit together
in my mind.

This code is also largely specific to DNS, but I wouldn't be against
putting this under its own namespace, since the end purpose *is* to make
an application.

Take a quick look at the overview POD in wiki format on github
https://github.com/warewolf/Net-DNS-Sinkhole/wiki/Overview (still being
drafted) and tell me what you think.  I'm not stuck on the name, and I
realize that it's your responsibility to ensure namespaces don't get
polluted.

Thanks,
Richard

Reply via email to