On Thu, Aug 24, 2000 at 01:32:10PM -0400, Joshua N Pritikin <[EMAIL PROTECTED]>
wrote:
> > 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 pro
On Wed, Aug 23, 2000 at 11:08:26AM +0200, Marc Lehmann wrote:
> As I read the documentation, Event->io should accept a GLOB
> reference as argument, but I cannot get this to work (it only works
> with some glob references, e.g. ones created by IO::Handle):
>
>use Event;
>
>my $fh = do {
On Thu, Aug 24, 2000 at 07:19:38PM +0200, [EMAIL PROTECTED] wrote:
> 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 extensio
On Thu, Aug 24, 2000 at 01:09:57PM -0400, Uri Guttman <[EMAIL PROTECTED]> wrote:
> please quote the docs that show this. according to my solaris 7 docs,
> you have to call aio_wait to get an aio_result back. this can be one of
I am talking about SIGIO and friends, not the posix aio_*-functions. a
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
> "ML" == Marc Lehmann <[EMAIL PROTECTED]> writes:
ML> Solaris can tell you which event caused the signal, so there is no
ML> need to scan your list of operations. After all, that's the point
ML> of sigio.
please quote the docs that show this. according to my solaris 7 docs,
you have t
On Thu, Aug 24, 2000 at 06:13:03PM +0200, [EMAIL PROTECTED] wrote:
> I forgot to mention that there are a lot of other ways to implement asynch
> i/o, for example you could just transfer the data inside the signal
> handler ;)
THAT's portable. :-)
> However, as for Event I think one could imple
On Thu, Aug 24, 2000 at 11:45:35AM -0400, Joshua N Pritikin <[EMAIL PROTECTED]>
wrote:
> > Just as linux: you clone/block/signal (i am not talking about pthreads). Its
I forgot to mention that there are a lot of other ways to implement asynch
i/o, for example you could just transfer the data ins
On Thu, Aug 24, 2000 at 05:34:58PM +0200, [EMAIL PROTECTED] wrote:
> On Wed, Aug 23, 2000 at 02:50:51PM -0400, Uri Guttman <[EMAIL PROTECTED]> wrote:
> > solaris has true aynch file i/o.
>
> Just as linux: you clone/block/signal (i am not talking about pthreads). Its
> just implemented differentl
On Wed, Aug 23, 2000 at 02:50:51PM -0400, Uri Guttman <[EMAIL PROTECTED]> wrote:
> solaris has true aynch file i/o.
Just as linux: you clone/block/signal (i am not talking about pthreads). Its
just implemented differently. And the posix aio functions do not use this
approach and are rather slow,
On Wed, Aug 23, 2000 at 11:17:20AM -0400, Joshua N Pritikin <[EMAIL PROTECTED]>
wrote:
> > please show me where in linux is the support for asynch file I/O. i have
> > not found it.
>
> Agreed. SIGIO != asynchronous I/O; SIGIO is a hack.
First of all, SIGIO *is* very nice if you want to do aio
On Wed, Aug 23, 2000 at 11:12:01AM -0400, Uri Guttman <[EMAIL PROTECTED]> wrote:
> > "ML" == Marc Lehmann <[EMAIL PROTECTED]> writes:
>
> ML> Well, most unices support asynchroneous I/O, which gives most of the same
> ML> and scales very well.
>
> please show me where in linux is the sup
On Wed, Aug 23, 2000 at 04:27:26PM +0100, Mike Guy <[EMAIL PROTECTED]> wrote:
> > reference as argument, but I cannot get this to work (it only works
> > with some glob references, e.g. ones created by IO::Handle):
>
> In your example, you have a glob, not a glob reference. They're
> different
13 matches
Mail list logo
