I suggest that given POE's start as something like a MUD and the fact that anything worth calling simply "MUD" needs to be very widely scoped and generic, you name your module something other than POE::Server::MUD.
Perhaps simply POE::Server::(NameOfYourMUD) or POE::Server::MUD::(NameOfYourMUD). Also the latter implies that a generic MUD framework exists and that your module uses it. I strongly prefer the former given that a MUD doesn't usually use a specific protocol, just plain text, so it's better given the name of your specific software product. If someone else writes a MUD what namespace will it occupy?
At any rate POE::Server::MUD is asinine since MUD isn't at all equivalent to TCP or IRC or whatever.
Given POE's roots, something using a generic MUD namespace had better be nearly as comprehensive as POE itself.
I agree, and after reading my last post on this subject i ended up naming it POE::Server::MUD::MassiveMUD, using MUD as more of a catagory then a module dependency (for the same reasons you mentioned).
I apologize if i offended any MUD creators out there :)
Exide Arabellan www.arabellan.com
