On Thu, Aug 24, 2000 at 12:29:24PM -0400, Joshua N Pritikin <[EMAIL PROTECTED]>
wrote:
> > i/o, for example you could just transfer the data inside the signal
> > handler ;)
>
> THAT's portable. :-)
Well, at least so much as using SIGIO. It only works this way on newer
systems, and I *do* care for a lot of old unix machines (why upgrade from
hp-ux 9.0 if it works? ;)
> > setup-phase:
> > then the event loop becomes:
>
> Sure, the hard part is working code. ;-)
Well, it really isn't more complicated. The complication really is the
configure stage (which should be done at runtime) where the method is
selected ;)
(And yes, I *am* actively trying to stay out of the "yet another project"
business ;)
> > the number of events becomes too large for the event queue. The phhttpd
>
> If they got it to work then perhaps we can borrow some code.
It has the "only tested under linux" stamp, of course ;) And they don't
care for configurstion, just for "make sure your system supports it".
However, my concern was the impression of "there is no portable event
mechanism we could use" that I got on the mailinglist, which becomes
increasingly untrue (sigio & friends (like sigtimedwait) are optional
posix extensions that get really popular), and the more programs are using
it the more "standard" it will become.
It would be hard work to implement this for Event (for the rare acses it
is realyl necessary), so I don't say this should have high priority, I
just wanted to say that it makes more sense in using some *standardized*
technique than using any os-specific extension.
> Well, I haven't disappeared yet and I'm sure that a new maintainer could
> be procured, if necessary.
Well... :) It was fine as it has been, so why change a running syst...? ;)
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
