CompuServe Messages

[Continued] PipeHandler "An AmigaDOS pipe device which supports OPEN, CLOSE, READ, WRITE, LOCK, EXAMINE, and EXNEXT. [My note: these are AmigaDOS standard messages to file system devices, I believe.] Thus you can have "named pipes". It also supports "taps" on a pipe, to capture all data flowing through the pipe. Author: Ed Puckett" Disk #84. APipe "An 'Amiga pipe' device…. Author: Per Bojson" Disk #601 FifoLib "FIFO: is like PIPE: but is based on fifo.library rather than its own implementation. Fifo.library is a general fifo library implementation that supports named fifos, writing to a fifo from a hardware exception, multiple readers on a fifo with each getting the same data stream, efficient reading, and an automatic or manual flow control. Programs that require non-blocking IO can access one side of a FIFO: connection via the fifo.library [my note: Amiga shared run- time library] instead of the FIFO: device…. Author: Matt Dillon" Disk #588 SKsh "A ksh-like shell for the Amiga. Some of its features include … [my note: many ksh features], I/O redirection, pipes, …. Author: Steve Koren" IPDevice "… A pipe-like DOS device that passes data immediately rather than waiting until a buffer is full. It also allows multiple writers to a single channel, maintained connections, and piped connections to a Shell. Author: Pete Goodeve" Disk #374 I'd also check out Matt Dillon's latest UUCP (on a Fish disk), ARP (basically extends an earlier version of AmigaDOS, but still somewhat popular, I think), because several facilities tag along with these packages, and talk to some Amiga gurus. A lot of them would probably be extremely happy to offer some help. I can't believe this problem cannot be overcome without rewriting the Amiga system software. I'm not currently competant to give specific help on this subject (although I think I've delved into Unix I/O, processes, pipes, etc. pretty deeply). I wish you could explain exactly what you are trying to do so I could understand it. If it would help, we could use Bach's book on the Unix kernel as a reference point (especially to clarify our language). If you could show me your relevant code, it would help. I'd be willing to look into this problem a bit, as my time allows. I'd like to see it worked out.