On Fri, Dec 17, 1999 at 09:59:51AM -0500, [EMAIL PROTECTED] wrote:
> >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.
What is not pretty about it? That looks OK...?
> Would:
>
> my $rv = Event->rvloop(); # Kind of 'inherited' loop/watcher
> $rv->listen(....)
>
> be better?
I have no idea!
> 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.
Yes... I'm not sure what you're asking.
> Sadly, working for a financial house, it's gonna be pretty hard work for me to
> give my code back to the community.
I suppose it depends on your manager. I work in the financial community
too.
> (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.
--
"Does `competition' have an abstract purpose?"
via, but not speaking for Deutsche Bank
