On 08 Nov 2000 12:46:19 +0100, Andreas J. Koenig wrote:
>>>>>> On Tue, 7 Nov 2000 19:14:54 +0000, Michael Stevens <[EMAIL PROTECTED]> said:
>
> > Modules:
>
> > POE::Component::RSS DSLI = bdpO "Event based RSS interface"
> > POE::Component::SubWrapper DSLI = bdpO "Event based Module interface"
>
>If Rocco (CC'd) believes that POE needs more exposure on the module
>list, we could list a few more package names below POE. Currently only
>POE::Kernel and POE::Session are listed.
>
>>From my limited point of view I get the impression that namespace
>management within POE is still self-regulating, but as said, C<we're
>open>
Good morning!
I think the POE::Component::* modules should be listed. 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.
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.
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.
-- Rocco Caputo / [EMAIL PROTECTED]
