From: "LiteStar numnums" <litestar@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Shared Library Service?
Date: Fri, 16 Jun 2006 20:14:01 -0400 [thread overview]
Message-ID: <283f5df10606161714m60ac8ddclcdae227519fa4768@mail.gmail.com> (raw)
In-Reply-To: <20060616234551.GM9881@submarine>
[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]
That's exactly what I figured.
And I was thinking FastCGI, which describes a protocol of comm. betwixt web
server & application, not
plain CGI.
On 6/16/06, Roman Shaposhnick <rvs@sun.com> wrote:
>
> On Fri, Jun 16, 2006 at 08:01:47AM -0400, LiteStar numnums wrote:
> >
> > Hello all,
> > Had an odd idea: shared library service...
> > Executables placed in,say, /lib/shsvc, would be executed with pipes
> > redirected to a mounted service (for now /n/shsvc).
> > The file server at /n/shvc simply has files for each library loaded.
> > An application that wishes to use the service
> > can simply open a file handle to /n/shvc/library & simply read/write
> > to the library file using a FastCGI/SCGI like
> > protocol. The file service could do some simple checks on the data
> > (making sure it's actually protocol data, &c),
> > and handle if a 'library' puked while working. This may not make as
> > much sense as I thought, since I am writing
> > this after only two hours sleep...
>
> This sounds a bit like what I had in mind for writing simple
> file servers. Basically the ammount of bookkeeping in lib9p
> is bit too much for simple things like having an rc script
> to serve a dynamic one-level tree, etc.
>
> On a practical level it didn't quite pan out, though. The complexity
> of the scripts and such was enough of a reason to switch to C and
> use lib9p directly.
>
> Thanks,
> Roman.
>
--
Lead thou me on, O Zeus, and Destiny,
To that goal long ago to me assigned.
I'll follow and not falter; if my will
Prove weak and craven, still I'll follow on.
-- Epictetus
He who enters his wife's dressing room is a philosopher or a fool. -- Balzac
[-- Attachment #2: Type: text/html, Size: 2452 bytes --]
next prev parent reply other threads:[~2006-06-17 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 12:01 LiteStar numnums
2006-06-16 23:45 ` Roman Shaposhnick
2006-06-17 0:14 ` LiteStar numnums [this message]
[not found] <000101c6913e$8d321f70$14aaa8c0@utelsystems.local>
2006-06-16 12:25 ` "Nils O. Selåsdal"
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=283f5df10606161714m60ac8ddclcdae227519fa4768@mail.gmail.com \
--to=litestar@gmail.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).