[I am not on the list, please consider sending me a cc]
Hi,
While developing Net-FCP, I implemented a very primitive wrapper around
the Event, Coro::Event, Glib and Tk event models - it basically offers a
somewhat limited Event-like API on top of whatever event library is loaded
(or can be autodetected).
I haven't seen something similar on CPAN yet (but I am blind), and since
the problem (using Event-driven I/O in modules) is definitely real (at
least for me), having a library that offers me simple readable/writable
events, signals (not unix-signals but general "wait for something async to
happen") that work under Gtk2 _and_ Tk _and_ Event etc. seems useful.
That's why I think unbundling this functionality into a somewhat cleaner
module is useful.
I don't know which name to use, though. AnyEvent (a'la AnyDBM) comes to
mind. Or maybe Event::Generic (bah), or..
Here is a summary of what it would be and what it wouldn't be:
+ It abstracts readable/writable events on sockets or pipes.
+ It abstracts certain forms of signalling.
+ Maybe timeouts (that is difficult already :)
- It won't be the definite library for everything (I don't want to set
a kind of event standard), just a bandaid to enable module users
using some form of event mechanism without forcing every user
to do the same.
I'd be happy to hear suggestions about a) wether this is useful at all
b) how it should be named.
TIA,
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
