Path: utzoo!mnetor!uunet!husc6!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!hplabs!well!shf
From: shf@well.UUCP (Stuart H. Ferguson)
Newsgroups: comp.sys.amiga
Subject: Re: IPC - A proposal
Message-ID: <5397@well.UUCP>
Date: 9 Mar 88 08:15:20 GMT
References: <5375@well.UUCP> <739@nuchat.UUCP>
Reply-To: shf@well.UUCP (Stuart H. Ferguson)
Organization: The Blue Planet
Lines: 42


>peter@nuchat.UUCP (Peter da Silva) says:
>In article <5375@well.UUCP>, shf@well.UUCP (Stuart H. Ferguson) writes:
>> inter-process communication.  With products like ARexx and Browser coming
>> out, we may get stuck with a "de-facto" standard which may not be well
>> designed, or several "standards" that are mutually incompatable.  ("It's
>> supports ARexx, but does it support Browser?")
>
>I'm insulted.
>The Browser Message will be of this form:
   [format deleted]
>You loacte the port to send this message with FindPort("BROWSER");
>Any objections?

I was actually refering to another message of yours:

   >From: peter@nuchat.UUCP (Peter da Silva)
   Newsgroups: comp.sys.amiga
   Subject: Browser 2.0 idea.
   Message-ID: <724@nuchat.UUCP>

|Anybody have any nifty ideas for what I can do with a public message port
|in Browser?
...
|Or how about "Hi, I want to be a tool. When you want me to wake up just send
|the WBStartup message to this port."
|Or how about "Hi, I want to be a tool. Just give me WBStartup messages to
|this port when someone drops files in this window."
|Anyone interested in becoming integrated?

These kinds of messages are the type that are of general interest to 
many programs in a message-passing, tools-intensive environment such as 
the one we're envisioning.  As such they should probably be part of a 
standard message protocol so that Browser and other programs can exist 
in peace and harmony.

To some extent, the IPC discussion is a reply to your question about 
"nifty ideas..."  I just picked Browser and Arexx as random examples of 
the NEED for a standard -- no insult intended.
-- 
		Stuart Ferguson		(shf@well.UUCP)
		Action by HAVOC		(shf@Solar.Stanford.EDU)