# fork or pthread for async I/O?

From: Ingo Wilken (Ingo.Wilken@Informatik.Uni-Oldenburg.DE)
Date: Wed Feb 02 2000 - 12:58:49 PST

- Next message: Peter J Jones: "xscanimage and Gimp Menu Location"
  - Previous message: Karl Heinz Kremer: "Re: Possible odd coincidence? (was Re: Problem compiling sane-1.0.1 frontend...)"
  - Next in thread: msitkows@au1.ibm.com: "Re: fork or pthread for async I/O?"
  - Reply: msitkows@au1.ibm.com: "Re: fork or pthread for async I/O?"
  - Reply: Yuri Dario: "Re: fork or pthread for async I/O?"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  Hi

  I'm currently thinking about using POSIX threads to implement asynchronous
  I/O in my backend. Most backends that currently implement asynchronous
  I/O do so by creating a pipe and fork()ing a reader process. Since this
  already requires POSIX support (pipe(), fork()), requiring pthreads for
  a backend should not be much of a problem? The backend could fall back
  to simple synchronous I/O if pthreads are not available (check at
  compile-time).

  Regards,
  Ingo

      --
      Source code, list archive, and docs: http://www.mostang.com/sane/
      To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

  - Next message: Peter J Jones: "xscanimage and Gimp Menu Location"
  - Previous message: Karl Heinz Kremer: "Re: Possible odd coincidence? (was Re: Problem compiling sane-1.0.1 frontend...)"
  - Next in thread: msitkows@au1.ibm.com: "Re: fork or pthread for async I/O?"
  - Reply: msitkows@au1.ibm.com: "Re: fork or pthread for async I/O?"
  - Reply: Yuri Dario: "Re: fork or pthread for async I/O?"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  This archive was generated by hypermail 2b29 : Wed Feb 02 2000 - 13:18:56 PST