home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!sun-barr!olivea!spool.mu.edu!umn.edu!news2.cis.umn.edu!gopher-news-request@boombox.micro.umn.edu
- From: BDESIMON@uga.cc.uga.edu (Bert)
- Newsgroups: comp.infosystems.gopher
- Subject: Re: T Type and PCG2 1.05
- Message-ID: <9209111758.AA24245@boombox.micro.umn.edu>
- Date: 11 Sep 92 17:18:58 GMT
- References: Your message of Fri, 11 Sep 92 10:51:56 CDT
- Sender: news@news2.cis.umn.edu
- Distribution: comp
- Lines: 25
- Approved: comp.infosystems.gopher@news.cis.umn.edu
- Original-To: Daniel Torrey <daniel@bauhaus>,
- Gopher Folks <gopher-news@boombox.micro.umn.edu>
-
- On Fri, 11 Sep 92 10:51:56 CDT Daniel Torrey said the following
- concerning adding type "T" support the the PC Gopher II client:
-
- <<<<<Daniel, I apologize for not giving up and going away -- bd>>>>
-
- >All I have to go on is the protocol document that I was given. It
- >defines the types "0" through "9", and states that the types "A"
- >through "Z" are "reserved". I'm not sure what that means, but since
- >there's no reference to "T" types in the protocol, I don't have any
- >plans to support them.
-
- Bummer ... this kinda puts me between a rock and a hard place.
-
- Our library requires tn3270 access, as well as do several other libraries.
- I could, of course, create the link to our library as type 8 telnet, but
- this really impacts the Mac folks. The Mac client is type T compliant, and a
- proper tn3270 settings file is created for type T. If it is type 8, an NCSA
- settings file is created, which doesn't do at all. And, you know, the
- CMS client and Unix client are type T compliant, too.
-
- ---------------------------------------
- | Albert DeSimone, Jr. |
- | BITNET: bdesimon@uga |
- | Internet: bdesimon@uga.cc.uga.edu |
- ---------------------------------------
-