Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!enea!tut!santra!jmunkki From: jmunkki@santra.HUT.FI (Juri Munkki) Newsgroups: comp.sys.mac.programmer Subject: Re: Task-to-task communication under MultiFinder Message-ID: <13942@santra.UUCP> Date: 21 Jun 88 20:14:55 GMT References: <586@iraun1.ira.uka.de> Sender: jmunkki@santra.UUCP Reply-To: jmunkki@santra.UUCP (Juri Munkki) Organization: Helsinki University of Technology, Finland Lines: 26 In article <586@iraun1.ira.uka.de> thschulz@iraul1.ira.uka.de (Thomas Schulz) writes: >How will the communication protocol / language look like ? >Clipboard usage as in Switcher ? AppleTalk ? TCP/IP ? Remote >Procedure Calls ? Sockets ? _________ AppleTalk already works under MultiFinder. All you have to do is to temporary enable the "selfsend" flag using the call introduced in Inside Macintosh V. You can then use ATP or even DDP to communicate the data. If you use DDP, remember that A5 will not point to your globals. You have to store A5 so that you socket listener can find it. Otherwise DDP is better, since it reduces buffer copying. >Does anybody else work on projects with communicating >applications on the same Mac? I only had one Mac at home at the time I tried to learn to program AppleTalk. I tested my NBP and ATP knowledge by writing two programs that communicated using these protocols. Please note that it is still much easier to use two (preferably three) macs to learn appletalk. You have to call GetNextEvent to allow MultiFinder to juggle. Juri Munkki jmunkki@santra.hut.fi jmunkki@fingate.bitnet