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

9P2000 message definitions, and protocol implementations #41

Closed
wants to merge 3 commits into from

Conversation

hugelgupf
Copy link
Owner

But no LegacyFile provided, and no testing done at all yet.

@hugelgupf hugelgupf force-pushed the 9p2000 branch 2 times, most recently from 8c410c1 to bcb5bc2 Compare July 28, 2020 07:07
This is a pre-cursor to supporting 9P2000, where some messages may
overlap. Sessions should allow us to change the version & message
registry.

9P2000 spec / Plan 9 man page for version(5):

"If the server does not understand the client's version string, it
should respond with an Rversion message (not Rerror) with the version
string the 7 characters "unknown"."

"A successful version request initializes the connection. All
outstanding I/O on the connection is aborted; all active fids are freed
(clunked) automatically. The set of messages between version requests
is called a session."

Signed-off-by: Chris Koch <[email protected]>
Signed-off-by: Chris Koch <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant