Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!accuvax.nwu.edu!nucsrl!gore
From: gore@eecs.nwu.edu (Jacob Gore)
Newsgroups: comp.sys.amiga
Subject: Re: Dnet2.0
Message-ID: <10260018@eecs.nwu.edu>
Date: 7 May 89 03:40:15 GMT
References: <6974@etana.tut.fi>
Organization: Northwestern U, Evanston IL, USA
Lines: 25

/ comp.sys.amiga / deven@pawl.rpi.edu (Deven Corzine) / May  5, 1989 /
>If this terminal server uses the
>TELNET protocol, then you're shit outta luck.  DNet will NOT run over
>_telnet_, because even though the telnet protocol is a full 8-bit data
>path, it isn't *quite* transparent enough.  [lists possible problems]

There is a telnet binary mode, and the terminal server may support it.

>The other major point of
>nontransparency in telnet is the escape character, usually ^].

That's a function of the telnet user interface, not of the protocol itself.
The terminal server may allow you to change it to another character, or
disable it altogether.

>On the other hand, the rlogin protocol IS transparent enough to run
>dnet over.

I'm surprised you haven't pointed out that "\n~", if followed by a command
that rlogin recognizes (such as "^Z", ".", etc.), is an escape sequence,
and needs to be disabled too (granted, it is less likely to occur in a
random data stream, but...)

Jacob Gore				Gore@EECS.NWU.Edu
Northwestern Univ., EECS Dept.		{oddjob,chinet,att}!nucsrl!gore