>I do not expect Event to require a CPAN size namespace. How many
>different types of event watchers do you need?
>What strange application problem are you trying to solve?
It's a simple TIBCO publish subscribe protocol, so in theory I just need two
watchers, a listener and and a sender (a sender not really being a watcher,
but causes timers, ios etc to be created). However, the protocol session
requires some initialization, and you can have multiple sessions in one event
loop. My current syntax is:
my $rv = new RV;
$rv->send(....);
$rv->listen(....);
This is all done implicitly using Event. Not pretty.
Would:
my $rv = Event->rvloop(); # Kind of 'inherited' loop/watcher
$rv->listen(....)
be better?
I have thought of using an 'has-a' relationship, but this is rather wordy.
my $rv = new RV;
Event->rvlisten(rv_session => $rv, ....)
However, if I did use this, what are the benefits of being a "registered"
watcher. Do I get to leave certain properties (desc, hits, timeout etc) for
the Watcher class to handle. I assume this would require me to follow some
standard function naming conventions so the loop could &stop and &start my
watchers if it wanted.
Sadly, working for a financial house, it's gonna be pretty hard work for me to
give my code back to the community. (I hope I might be able to follow the lead
set by Philip Moores "Artistic License basis for Financial Industry Open
Source"). Even so, if I can thrash out the theory in the open, it should
provide a lead to people doing the same thing.
Regards,
Gavin
____________________________________________________________________
Get free email and a permanent address at http://www.amexmail.com/?A=1
