After a talk in #poe, I was assigned with the task of coming up with
some guidelines for POE components.
I'd like as much feedback as I can get. Then I'll setup a page on
poe.perl.org with what everyone has came up with, and hopefully some
guidelines will come of this.
Here's what we have so far
Hi, I have created a modest PoCo for making TCP proxies, that is
sessions that connect to a server when connected to by a client,
and that also execute callbacks as info flows both ways. I would
appreciate comments and bug reports, especially before I post a
dist to CPAN. The sf project is called n
On (07/25 16:56), David Davis wrote:
> -interchangeable events & coderefs
> event => 'event',
> event => \&event,
this was decided against years ago. components act like services.
accepting event names causes the code in question to mutate an existing
session to its will. this is what wheels are
On (07/25 16:56), David Davis wrote:
> -call conventions (use hashrefs instead of arrays?)
are you talking about the insides of a component object? if so, don't
meddle there. any guidelines for components really need to stick to
interface alone. let the components do what is necessary to get thei
I always prefer more flexibility so one thing I'd like to see is call
signatures that can take a hash or list of hashrefs so I can write:
$y = { three => 'tre' };
$x->(one => 'ett', two => 'tva', $y, etc => 'whatever');
-Original Message-
From: sungo [mailto:[EMAIL PROTECT
Erick Calder wrote:
I always prefer more flexibility so one thing I'd like to see is call
signatures that can take a hash or list of hashrefs so I can write:
$y = { three => 'tre' };
$x->(one => 'ett', two => 'tva', $y, etc => 'whatever');
The following should work without any chang
