I'm trying to create a new perl Event watcher type for a C++ messaging API
that my company uses.
Embedding the perl event loop, and creating watchers that mimic the behavior
of the perl ones has been surprisingly easy. However I see, from looking at
Event::tcpsession and process.pm, that the Event::Watcher class has some
"registry" functions. Is this what I think it is - some standard wrappers for
custom watchers.
Is there a recommended way to use this (or is it Joshua's privilege, and I
should keep out?).
As far as I can see, the register function also creates a watcher constructor
of the form:
Modules::A::B ==> Event->B()
.. this looks disaster bound if someone else writes Other::C::B. Is there a
view on module naming conventions? Currently it seems to be Event::Foo::Bar
etc.
I realize that Event is still in flux, but I would rather not reinvent the
wheel if it's not absolutely essential.
Regards,
Gavin Brock
____________________________________________________________________
Get free email and a permanent address at http://www.amexmail.com/?A=1
