>>>>> "MGS" == Michael G Schwern <[EMAIL PROTECTED]> writes:
MGS> As I understand it, there is currently no agreed upon common event
MGS> loop architecture in Perl. This means that if two event-based modules
MGS> are used together (say, Net::IRC and POE) the one who's main loop
MGS> starts up first will win.
MGS> So the question I put to you all is, would it make sense for Perl to
MGS> have a common event loop from which all other modules can then draw,
MGS> thus avoiding the current state of conflict? Or will a stable
MGS> threading implementation provide the equivalent?
i have a rfc on that in the works. it has been discussed and many people
want such a beast. it is best integrated into the core as it has to have
clean delivery of events and signals.
threads can't provide the same support as events, especially for stuff
like tk or stem (my new product). events and threads can live together
in one process as well.
uri
--
Uri Guttman --------- [EMAIL PROTECTED] ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
