Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test and debug medley networking code #456

Closed
masinter opened this issue Sep 4, 2021 · 1 comment
Closed

test and debug medley networking code #456

masinter opened this issue Sep 4, 2021 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@masinter
Copy link
Member

masinter commented Sep 4, 2021

This is a placeholder for comments and elaboration of ideas for how to restore Medley networking functions.

There is the "Dodo" project which has multiple server implementations.

https://github.com/devhawala/dodo

The ContraltoJS project includes an alto emulator that could be used to wire up Medley implementations of PUP protocols.

@nbriggs nbriggs added the maiko label Sep 27, 2021
@masinter
Copy link
Member Author

Other "network" issues

#573 Set up and test networking
#786 need TCPOPS

Here's a summary of the situation -- please update

There are three protocol "stacks" -- PUP, XNS, and TCP/IP.
There are Lisp implementations of XNS and PUP based on packet-level SUBRs in Maiko.
The SUBRs though are based on an obsolete Sun interface (?). TCP/IP has a similar situation

Getting the network running isn't very interesting unless we can talk to other instances of medley or some of he other XNS or PUP implementations.

Loading networking files were moved to the end of LOADUP-LISP.
(PUP 10MBDRIVER LEAF LLETHER DPUPFTP LOCALFILE DSKDISPLAY COURIER LLNS TRSERVER SPP NSPRINT
AUTHENTICATION BSP CLEARINGHOUSE NSFILING MAIKOETHER)

We took NFS and X11 support out of Medley because they were older versions.

@masinter masinter added the duplicate This issue or pull request already exists label Aug 11, 2022
@masinter masinter closed this as not planned Won't fix, can't repro, duplicate, stale Aug 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants