in reply to Need help naming a module
If you're not replacing Apache::ASP entirely then perhaps naming your version after what it does different... If you add some .net type syntax to Apache::ASP then perhaps Apache::ASP::DotNet, or as you say, if you uses less resources go with Apache::ASP::Lite.
If yours is just a different implementation, you may want to be Apache::ASP::Backend::Foo or Apache::ASP::XS and arrange for your implementation to be to be chosen by Apache::ASP based on pseudo-random number generation, the cycle of the moon or similar...
You want your name to be similar to the name of other things that do what you do, so that you turn up when people search for obvious things. If you find people are getting confused, you just need to include a link in your POD to the module that you're being confused with.
@_=qw; ask f00li5h to appear and remain for a moment of pretend better than a lifetime;;s;;@_[map hex,split'',B204316D8C2A4516DE];;y/05/os/&print;
Update - removed links in favour of <c>'s
|
|---|