9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Roman Shaposhnick <rvs@sun.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 16:45:51 -0700	[thread overview]
Message-ID: <20060616234551.GM9881@submarine> (raw)
In-Reply-To: <283f5df10606160501y5dc0ad22ga4f64426b24e2ec1@mail.gmail.com>

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.


  reply	other threads:[~2006-06-16 23:45 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 [this message]
2006-06-17  0:14   ` LiteStar numnums
     [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=20060616234551.GM9881@submarine \
    --to=rvs@sun.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).