shf@well.UUCP (Stuart H. Ferguson) (04/26/88)
I've written up a technical specification for an object-oriented
InterProcess Communication standard. It should be very readable even
though it is nearly 700 lines in length, since it's written as a user
document and describes the system to someone who would want to program for
it.
I would much appreciate feedback on the design and suggestions as to
improvements and enhancements. Constructive criticism is welcome; flames
will be tolerated. Areas that need work are:
Asynchronous and Recursive Message Passing
I've concentrated mostly on synchronous message passing so need to
know what to include in the asynchronous cases.
Error Conditions and Signaling Errors
Something better than the `ERR' class object?
Bizarre race conditions I didn't think of ...?
The "Command" (Message) structure
Perhaps Pete/Peter could summerize the results of the discussion they
had with regard to this issue.
Network Adaptability
People have mentioned making IPC work on a distributed system and I'm
game, but I'm not familiar with the issues. Just what is required?
Put in a good word at DevCon and the May BADGe meeting since I will not be
at either.
--
Stuart Ferguson (shf@well.UUCP)
Action by HAVOC (shf@Solar.Stanford.EDU)