From: Enrico Weigelt <weigelt@metux.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] Paper on 9P and synthetic filesystems
Date: Wed, 12 Dec 2007 12:59:31 +0100 [thread overview]
Message-ID: <20071212115929.GA31954@nibiru.local> (raw)
Hi folks,
is there any paper which shows the benefits of synthetic filesystems
for application software development ?
I'd like to show people in several other projects (eg. moz) why
it's good to split large applications into several subsystems
speaking to each other via synthetic filesystems (eg. instead
of individual IPC mechanisms).
thx
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
next reply other threads:[~2007-12-12 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 11:59 Enrico Weigelt [this message]
2007-12-12 12:06 ` Francisco J Ballesteros
2007-12-12 19:49 ` Uriel
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=20071212115929.GA31954@nibiru.local \
--to=weigelt@metux.de \
--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).