On Wed, Aug 18, 2004 at 10:51:29PM -0700, Erick Calder wrote: > > It allows people to publish modules autonomously. > > using POE:: shouldn't present any problem with this
This is technically true. Only politeness prevents people from dropping modules into someone else's namespace. Politeness turns out to be a strong pattern in the Perl community. I designated "POE::Component" as an open space where people could put modules without asking and without feeling guilty about it. Nobody would not need to review them for "sufficient POEness", whatever that is. > > It avoids name collision between "core" POE and third-party > > components. > > avoided via the use of POE::Core You seem to be suggesting that we break every existing POE program. That sounds extreme, especially when there are alternatives that don't break anything. Also I'm under the impression that we're discussing voluntary guidelines for new modules, not standards to enforce upon existing code. > > It implies a border between POE and all these things that must be > > installed separately. > > see above > > > Implies that all the modules have something in common. > > they have POE in common... beyond that POE:: simply provides a space to > create namespaces e.g. POE::Server for servers POE::Client for clients, etc. They would also have certain published interoperability practices in common. The guidelines for those practices are being worked out on this mailing list. This dialog is part of that process. A separate namespace would define a scope where those practices are standard. That way developers can safely assume modules within that scope operate in certain consistent ways. Making the scope "all of POE" would be bad. It would ghettoize anything that chose not to play along. People would feel bad if they didn't like the guidelines or want to use it, perhaps for quick hacks or large systems that just work better a different way. I guess I'd rather the system live or die by the strength of the patterns it describes than brute forcing everybody to use it. -- Rocco Caputo - http://poe.perl.org/
