Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!lll-lcc!ames!ucla-cs!cc1 From: cc1@ucla-cs.UUCP Newsgroups: comp.sys.amiga Subject: Networking Amiga's Message-ID: <5370@shemp.CS.UCLA.EDU> Date: Sat, 4-Apr-87 20:55:56 EST Article-I.D.: shemp.5370 Posted: Sat Apr 4 20:55:56 1987 Date-Received: Sun, 5-Apr-87 13:43:09 EST References: <2845@ecsvax.UUCP> <3018@jade.BERKELEY.EDU> <2866@well.UUCP> Sender: root@CS.UCLA.EDU Reply-To: michael@remsit.UUCP cc1@CS.UCLA.EDU (Michael Gersten) Organization: Ucla Computer Club (disclaimer) Lines: 39 Before everyone says, "I want this on a network hardware board", what about the software? In particular, all Amiga programs comunicate by messages. They give a START address and LENGTH. To a message port. What about mods to the message routines that will, when given a message port that corresponds to a networked machine, copy the memory TO THAT MACHINE, and give to a program over there? Presto! EVERY program instantly works over the network. NO modifications needed. The only question becomes: how do you tell if a port is on a different machine? How do you tell this machine that "port X is remote"? And finaly, how do you pass a remote port over? Suggestions (please try to cut these down, lets see if we can get a good specification from this for the 1.3 or network boards) Suggestion #1: All machines on the net have a number from 1 to 255. 0 is the current machine. The upper byte of the message port is used to specify the machine number. Advantage: Easy Disadvantage: A third type of memory (NOT-NET) for 68020 boards Suggestion #2: EXEC tracks which ports are local (via CreatePort() and a sorted tree). Advantage: No memory restrictions Disadvantage: What if two machines have a port at the same address? Which machine is that port on? (I have no third suggestion, anyone else?) Michael Gersten Views expressed here may not be those of the Computer Club, UCLA, or anyone in their left OR right mind. And that's the name o' that tune.