Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!mips!apple!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: rsm@math.arizona.edu (Robert S. Maier)
Newsgroups: comp.dcom.telecom
Subject: Prodigy Communications Protocol
Message-ID: <14775@accuvax.nwu.edu>
Date: 18 Nov 90 21:20:48 GMT
Sender: news@accuvax.nwu.edu
Organization: University of Arizona Mathematics Department
Lines: 20
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 830, Message 2 of 8


There have been a good many articles in TELECOM Digest complaining
about Prodigy.  Besides Prodigy's policies, many posters are irritated
by their inability to capture Prodigy output to a file.

Has anyone done anything about this?  I gather Prodigy uses a
proprietary communications protocol, but is it possible to
reverse-engineer it?  That would open the door to custom-designed
Prodigy clients, running on any architecture.  And it would facilitate
the addition of new features, such as capturing text and graphics
output.

Or is it simply too difficult a job?


Robert S. Maier   | Internet: rsm@math.arizona.edu
Dept. of Math.    | UUCP: uunet!arizona!amethyst!rsm
Univ. of Arizona  | Bitnet: maier@arizrvax
Tucson, AZ  85721 | FAX: +1 602 621 8322
U.S.A.            | Voice(POTS): +1 602 621 6893  /  +1 602 621 2617