Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!ucbvax!MC.LCS.MIT.EDU!KFL%MX.LCS.MIT.EDU
From: KFL%MX.LCS.MIT.EDU@MC.LCS.MIT.EDU.UUCP
Newsgroups: mod.computers.vax
Subject: Re: VMS and programmer unfriendliness
Message-ID: <[MX.LCS.MIT.EDU].932390.860710.KFL>
Date: Thu, 10-Jul-86 23:33:48 EDT
Article-I.D.: <[MX.LCS.MIT.EDU].932390.860710.KFL>
Posted: Thu Jul 10 23:33:48 1986
Date-Received: Sat, 12-Jul-86 01:20:00 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 16
Approved: info-vax@sri-kl.arpa


    From:     <JMS@ARIZMIS.BITNET> (A Virtually Vegetal Nonentity)

    In any case, the one problem I wanted to point out was your initial
    remarks about echoing.  FROM AN APPLICATION'S POINT OF VIEW, you're
    right.  Echo back at the host; hell, it knows the best stuff to
    echo anyway.

    However, as a network architect, I shudder whenever anyone talks about
    doing something like that.

  Making the packetizing invisible to the program should be done in the
OS, just as making the details of how virtual memory is mapped into
physical memory is mercifully taken care of.  I mean, this is why OS's
cost so much, right?
								...Keith