>>>>> On Wed, 08 Nov 2000 08:19:51 -0500 (EST), "Rocco Caputo" <[EMAIL PROTECTED]> said:
> I think the POE::Component::* modules should be listed.
So they will. (Actually while I typed this email, I already registered
Michael's two modules)
> They do useful
> things which aren't necessarily related to POE itself, and the whole
> purpose of POE::Component is to let people publish POE modules without
> waiting for me to include them in the main distribution.
> POE::Component is evolving as it goes. I've started putting my own
> components into two main categories, ::Client and ::Server, with the
> miscellaneous guts modules falling in the main namespace. It's my
> hope that establishing these buckets ahead of time will prompt people
> to use them instead of putting their modules just anywhere.
This doesn't make it clear to me if I should register P:C:Client and
P:C:Server.
> By way of example, some of my modules (yet to be CPANned) are at
> <http://poe.perl.org/poco/>. There also is POE::Component::Server::TCP
> in the main distribution.
This page looks to me like the start of a module list. If you expect
hundreds of small modules in there, then the PoCo namespace would
greatly reduce the typing requirements for the POE community, right?
Should we use PoCo instead of POE::Component? If so, it's easy for me
to change Michael's registrations.
> None of this is written in stone. If there's a better interface to the
> CPAN's structure, I'll be happy to promote and use it. If you would like
> to see the namespace hold a certain structure (or even be dispersed), I
> can document it in the POE::Component manpage.
No preference on my side.
Regards,
--
andreas
