Le 25 oct. 2010 à 20:52, Aristotle Pagaltzis a écrit :

> Hi David,
> 
> * David Morel <dmo...@amakuru.net> [2010-10-24 22:05]:
>> Thanks for taking the time to have a look (if you have some
>> time :) and for any useful suggestions (not even limited to
>> naming, since I never had a chance to release anything yet).
> 
> some prior art on the CPAN:
> 
> http://search.cpan.org/dist/Schedule-RateLimiter/RateLimiter.pm
> http://search.cpan.org/dist/Data-Throttler/Throttler.pm
> http://search.cpan.org/dist/Data-Throttler-Memcached/lib/Data/Throttler/Memcached.pm
> 
> The last one targets essentially the same problem space as your
> module, although it seems less powerful overall (with a somewhat
> simpler interface in exchange).

Now that you mention it, it is so similar in functionality, my
module could (or should) have been just a wrapper around it.
It's just a pity I didn't find it when I was looking for the 
functionality, and I wonder how that can be. Shame.

> I would say this does indeed belong in the Schedule:: TLNS.
> 
> (Data:: is the “I have no idea where to file this” namespace in
> many cases.)
> 
> BorderPatrol is a clever name, but unless you plan to expand it
> significantly to become more of a platform/framework, I still
> advise in favour of purely descriptive names over cutesy/brand/
> marketing names. Those have become more common on CPAN in recent
> years, when once upon a time it was *all* about the descriptive
> names. They can work well for modules with a large scope, but I
> believe they are a hindrance for modules with narrower focus.

Agreed. The original name was kind of a private joke, regarding some
problem I had with the real border police at the airport. But the 
joke is kind of lost if the module is released publicly, hence my 
request for name suggestions :) 

> So I would pick some name in Schedule:: that captures the mission
> statement for your module, especially as distinct from the other
> modules that already exist. Eg. something like AdaptiveThrottler
> (if I skimmed your POD right).

Thanks a *lot*!

David Morel

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to