>>>>> "AB" == Alan Burlison <[EMAIL PROTECTED]> writes:
AB> Uri Guttman wrote:
>> my scheme allows the user to do that. they just create a regular thread
>> and request all their signal events in that thread. but my design also
>> allows different threads to handle different signals (and multiple
>> threads to handle the same one).
AB> Hmm. So how will you know the difference betwen a signal being
AB> delivered once and handled twice and the same signal arriving twice? I
AB> can see that multiple threads all handling the same signal could be very
AB> confusing.
event.pm does that right now. it uses counters which bump for each real
signal that comes in and decrements for each one delivered. these
counters would be shared and locked. it doesn't sound too hard to
do. also like dan has been saying, there are certain restrictions we
could place on the coder like not allowing more than one handler for the
same signal even across threads.
>> my main point there is that faking async i/o and sync signal delivery is
>> much easier than faking threads. so we code all the internals to an
>> event loop api and fake it underneath as needed on various
>> platforms. much more on this soon.
AB> As Jarkko would say:
AB> Yes, yes yes.
AB> :-)
so stop bothering me so i can write up the damned thing.
:)
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
