9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] Copying pushtls(2)
Date: Fri,  8 Aug 2003 14:35:14 +0200	[thread overview]
Message-ID: <20030808143514.C1666@cackle.proxima.alt.za> (raw)

Can the technique used in pushtls(2) of passing an open file
descriptor to a filter device work with a user-space file server?

What would be the equivalent lib9p idiom?

Somehow, I can't imagine just handing an integer to a user-space
file server (a totally distinct executable) and thereafter presuming
that the latter will find it useable as a file handle.  What am I
missing?

If that technique is not viable, is there perhaps another mechanism
that can be used analogously?  An existing example would be a nice
pointer.

++L


             reply	other threads:[~2003-08-08 12:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-08 12:35 Lucio De Re [this message]
2003-08-08 13:29 ` David Presotto
2003-08-08 13:39   ` Lucio De Re
2003-08-08 13:42 ` C H Forsyth
2003-08-08 13:51   ` David Presotto
2003-08-08 13:51     ` Lucio De Re
2003-08-08 14:19       ` David Presotto
2003-08-08 14:32         ` Lucio De Re

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=20030808143514.C1666@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).