Agreed I think. It's just a matter of specifics now. The Net::Server::* namespace currently belongs to a suite of OO modules by one author (Net::Server, Net::Server::PreForkSimple, Net::Server::Proto::TCP, etc), and they all inherit from each other and have a consistent interface.

I would feel like I was polluting that to stick a module with a different interface into the exact same namespace. Also, Net::Server::* does TCP, UDP, and Unix sockets, whereas my module only covers TCP. And of course, mine's Linux-only, theirs is platform independant pure-perl.

So brings us back to your first 3-level suggestion, Net::TCPServer::Linux, I guess?

In the rest of the software world, people give their projects unique names, here in the CPAN world the norm seems to be descriptive names, which seems to make it difficult to have competing implementations in the same namespace. I guess that's the point to some degree, to encourage the idea that everyone contributes to one common best-of-breed implementation of whatever thing it is that category of module can do.