From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Porting to plan9 / PF_UNIX
Date: Sat, 14 Apr 2007 13:28:28 -0400 [thread overview]
Message-ID: <20070414172803.615971E8C26@holo.morphisms.net> (raw)
In-Reply-To: <45219fb00704141015if096876h1d5621b925fad1a@mail.gmail.com>
There is nothing in Plan 9 like a named socket.
There is /srv, which is like named pipes (the
difference is that named sockets distinguish
multiple connections to them).
If ts were a Plan 9 program, it would present a
file tree that could be manipulated to add things
to the queue or remove them or check their status,
instead of inventing a custom RPC protocol.
Then it would post a fd in /srv for 9P service,
and you'd mount /srv/ts /mnt/ts and then interact
with /mnt/ts via file operations. (Multiple programs
can mount /srv/ts because the kernel acts as a
multiplexor for 9P services -- the server sees only
one 9P conversation.)
Russ
next prev parent reply other threads:[~2007-04-14 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 15:34 Lluís Batlle
2007-04-14 15:55 ` W B Hacker
2007-04-14 17:15 ` Lluís Batlle
2007-04-14 17:28 ` Russ Cox [this message]
2007-04-14 17:44 ` Lluís Batlle
2007-04-14 21:17 ` ron minnich
2007-04-15 17:41 ` Lluís Batlle
2007-04-14 19:29 ` W B Hacker
2007-04-14 16:13 ` Francisco J Ballesteros
2007-04-14 17:01 ` Uriel
2007-04-14 21:28 ` John Stalker
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=20070414172803.615971E8C26@holo.morphisms.net \
--to=rsc@swtch.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).