From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <283f5df10606160501y5dc0ad22ga4f64426b24e2ec1@mail.gmail.com>
Date: Fri, 16 Jun 2006 08:01:47 -0400
From: "LiteStar numnums" <litestar@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_9150_8066145.1150459307273"
Subject: [9fans] Shared Library Service?
Topicbox-Message-UUID: 6b99171e-ead1-11e9-9d60-3106f5b1d025

------=_Part_9150_8066145.1150459307273
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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...
Cheers,
--Stefan

-- 
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

------=_Part_9150_8066145.1150459307273
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello all,<br>Had an odd idea: shared library service...<br>Executables placed in,say, /lib/shsvc, would be executed with pipes redirected to a mounted service (for now /n/shsvc).<br>The file server at /n/shvc simply has files for each library loaded. An application that wishes to use the service
<br>can simply open a file handle to /n/shvc/library &amp; simply read/write to the library file using a FastCGI/SCGI like<br>protocol. The file service could do some simple checks on the data (making sure it's actually protocol data, &amp;c),
<br>and handle if a 'library' puked while working. This may not make as much sense as I thought, since I am writing <br>this after only two hours sleep...<br>Cheers,<br>--Stefan<br clear="all"><br>-- <br>Lead thou me on, O Zeus, and Destiny,
<br>To that goal long ago to me assigned.<br>I'll follow and not falter; if my will<br>Prove weak and craven, still I'll follow on.<br> -- Epictetus<br><br>He who enters his wife's dressing room is a philosopher or a fool. -- Balzac

------=_Part_9150_8066145.1150459307273--