From: Ethan Gardener <eekee57@fastmail.fm>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Plumber architecture question
Date: Sat, 5 Jan 2019 08:47:53 +0000 [thread overview]
Message-ID: <1546678073.2540564.1626108336.2EFA366B@webmail.messagingengine.com> (raw)
Every so often, I start wondering why the plumber isn't simpler. Here's my simpler design: There is no plumber. Instead, `plumb` reads the plumbing files and acts accordingly. To receive input from the plumber, programs post a pipe in /srv. No need for a special-purpose filesystem.
It will break if multiple processes post the same pipe, the second process won't be able to create the pipe. Isn't that a good thing? Plumber behaviour is to send messages to all recipients, which has surprised me a few times when I wasn't quite alert.
It would also break my use case of separate plumber instances for separate activities; there is only one #s, but I don't think anyone does this other than me. It can be done another way, with plumber rules to discriminate by directory, but that takes a bit more setup. I would work if there could be multiple srv(3) filesystems, which I think would sometimes be useful for other tasks too. To make this work, all the programs which currently address '#s/filename' would have to be changed to address the full path. Then creation permission would control which of the srv filesystems gets the pipe.
Just musing on architecture. Comments welcome.
--
2.1.3. Life with eternal upgrades
next reply other threads:[~2019-01-05 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 8:47 Ethan Gardener [this message]
2019-01-05 14:12 ` erik quanstrom
2019-01-05 14:53 ` Ethan Gardener
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=1546678073.2540564.1626108336.2EFA366B@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
/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).