From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9P2000
Date: Wed, 31 Jan 2001 04:31:36 -0500 [thread overview]
Message-ID: <20010131093143.BA424199FA@mail.cse.psu.edu> (raw)
[I'm just confused trying to follow the argument. Feel free to ignore.]
Aren't there two issues here? One is resynchronizing
the message stream, so that both sides agree on the
message boundaries. The other is resynchronizing
the 9P conversation state, so that both sides agree
on which tags and fids are in use and what they mean.
Something (an underlying transport protocol, say) needs
to provide the first capability, but without the second
you're still hosed. In an IP environment, you can drop
and redial the connection, but if you've got a hard-wired
link, you need an explicit restart within the protocol,
hence Tsession, no?
Russ
next reply other threads:[~2001-01-31 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 9:31 Russ Cox [this message]
2001-01-31 17:46 ` Mike Haertel
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 2:18 rob pike
2001-01-31 2:16 rob pike
2001-01-31 8:56 ` Mike Haertel
2001-01-30 12:09 rog
2001-01-30 18:04 ` Mike Haertel
2001-01-27 21:58 rob pike
2001-01-28 16:29 ` Sam Ducksworth
2001-01-30 9:21 ` Mike Haertel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010131093143.BA424199FA@mail.cse.psu.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).