(Message May:64)
MessageName: (Message May:64)
SUBJECT: P-SYSTEM AND PORTS
Date:    Mon, 18 May 87 15:49:30 PDT
From:    FRANKLIN%CGEUGE51@BITGATE
To:      AMilne@UCICP6
----------------------------------------

Received: from BITNET by UCICP6 with PMDFs; 18 May 1987 15:49:18
Received: From CGEUGE51(FRANKLIN) by UCIVMSA with RSCS id 5000for AMILNE@UCIVMS
A; Mon, 18 May 87 15:46 PDT          
Date:     Mon, 18-MAY-1987 14:12 N
From:     FRANKLIN@CGEUGE51
X-From:     S Franklin <FRANKLIN@CGEUGE51>
X-To:       amilne@UCI
Original_To:  JNET%"amilne@UCI",JNET%"bork@UCI",IBRAHIM,LEVRAT,FRANKLIN
 
What's folks feelings on the following points:
    1) Continued use of the p-system as a stand alone system.
    2) Use of the p-system under MS-DOS
    3) Changing Ports so that instead of peaking and poking
       RAM to communicate information between programs instead
       we use a small amount of ramdisk for "files" that communicate
       this information.  More generally, creative use of ramdisk
       to speed program execution and inter-program communication.
    4) Alternatives to the p-system.
    5) Alternatives to UCSD Pascal.
    6) Assumptions regarding minimum (delivery) machine configurations.
    7) Network versions of software.
       (Just running programs across a network doesn't seem to
        be a very difficult problem although there are some cute
        parts about sharing copies as opposed to having only one
        station able to access any given copy of a program, cuteness
        which we think is going to be easily resolved shortly.
        I'm much more intereseted in the record keeping function
        across the network.  (You will recall (perhaps) some very
        nice work Bertrand and C. Kuhni did on the Davong/Tiara network.
        Bertrand is in the process of looking at more popular alternatives
        to this network for the EAO work here.)
     
-- sdf

==================================================