22 Nov
2022
22 Nov
'22
7:43 p.m.
On Nov 22, 2022, at 12:04 PM, Thomas DeBellis
<tommytimesharing(a)gmail.com> wrote:
On 11/22/22 8:46 AM, Johnny Billquist wrote:
That fits what I know, and documented in the protocol doc in the PyDECnet source tree.
Config is a required message from server to client. The RSTS and RSX protocol variants
then do a response config message from client to server, but the TOPS-20 variant does
not.
paul
On 2022-11-22 06:02, Thomas DeBellis wrote:
[...]
Trying to remember here, since it's now a few months since I looked at it. I think
that I later concluded that the server might sent an init, but the client is not
expecting/requiring it. Which would suggest that it might not be sent by all versions, so
it's not reliable. I don't think it sends any INIT either. It just starts running,
assuming it works on a stream of bytes with no further interpretation.
Hum...
Well, as I said, I am looking at the Tops-20 monitor code for the NRT terminal driver
(NRTSRV) and the two Tops-20 NRT clients that I am aware of (SETHOST and Kermit-20).
NRTSRV always sends the configuration message, but it does not wait for any response.
Trying to unravel some of this very informative
thread.
[...]
------------------------------------------------------------------------
On 11/21/22 5:52 PM, Johnny Billquist wrote:
You forget fast. :-)
Here is what I wrote in August this year:
[...]
So basically, the TOPS-20 NRT server is not sending anything when you connect,
Am I understanding you correctly? Are you sure about that? May I ask you to send me an
example where this happens? Paul's recollection agrees with my experience.