🚀 go-pugleaf

In article <6525@well.UUCP>, shf@well.UUCP (Stuart H. Ferguson) writes:
> 3.  Simple.  The design may be as complex as needed internally, but
> should be only as complex for the programmer as the task he wants to
> perform.  Things should be easiest for client programmers, thus making
> it simple even for novices to tap the power of existing servers. 

The design should be simple for servers, too. One of the reasons there
are so many filter programs on UNIX is that it's *easy* to write one:
at the lowest level it's just "main() { while(read) { process; write; }}".

None of the IPC systems so far satisfy this requirement.

Just about any program you write on the Amiga is going to have to handle
Exec messages. Making IPC look like Exec messages is actually easier
than making it look like something more elegant.

Item 0: it should be more efficient than pipes. This is a basic
	assumption we're all making, but it should be spelled out.

After all, named pipes satisfy most if not all of your requirements.
-- 
-- `-_-' Peter (have you hugged your wolf today?) da Silva.
--   U   Mail to ...!uunet!sugar!peter, flames to alt.dev.null.
-- "Running OS/2 on a '386 is like pulling your camper with an Indy car"