Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!gamma!mibte!fmsrl7!eecae!nancy!mailrus!ames!pasteur!ucbvax!USU.BITNET!SLMYQ
From: SLMYQ@USU.BITNET
Newsgroups: comp.sys.amiga.tech
Subject: Re: IPC
Message-ID: <8804050518.AA26309@jade.berkeley.edu>
Date: 5 Apr 88 05:18:00 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 14

All this IPC stuff seems to be pretty neato, but my question is, how will
application programmers use it?  It would be nice if a lowly mortal like
me could access this without going to great pains.  It should in a way be
as simple as the AmigaDOS library routines.  Also, it would be nice to be
able to get on the serving end easily.  Everybody who's tried knows how
hard it is to make your own AmigaDOS device driver (BCPL?  Blachk!) or
an Exec device.  I think it should be message based internally, but to
the application programmer it would just be a set of routines to call using
"IPC handles" returned by "IPC Open" routines or whatever.

I don't know if this is the purpose you're thinking of this stuff to be for,
but it would be nice for my program to call up the IPC library and say,
"Hey, I need this data compressed in 12-bit Lempel-Ziv format", or "Hey, I
want this FTXT file formatted into an ILBM picture".