Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!usc!apple!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: amanda@visix.com (Amanda Walker)
Newsgroups: comp.dcom.telecom
Subject: Re: Prodigy Communications Protocol
Message-ID: <15096@accuvax.nwu.edu>
Date: 30 Nov 90 04:49:07 GMT
Sender: news@accuvax.nwu.edu
Reply-To: Amanda Walker <amanda@visix.com>
Organization: Visix Software Inc., Reston, VA
Lines: 18
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 856, Message 1 of 12


In article <14869@accuvax.nwu.edu>, nelson%odin.corp.sgi.com@sgi.com
(Nelson Bolyard) writes:

> 'Twouldn't surprise me a bit to see that AT&T revived that technology 
> [NAPLPS] for Prodigy.

Back during my very brief tenure as a Prodigy user, I poked around
some in the Macintosh client software (trying to figure out why it was
so unfriendly to the rest of the Mac).  I ran across several pieces of
code that had debugging messages & debugger symbols which referred to
NAPLPS.  I never peered at the actual data stream, but all of the
screen displays are certainly well within the capability of vanilla
NAPLPS.  The first time I signed on, in fact, my first thought was,
"my god, this looks like Telidon back from the grave" :).


Amanda Walker