9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: [9fans] using Tree* and File* vs imlementing own 9p-handling routines?
Date: Thu,  8 Jan 2004 12:50:52 -0700	[thread overview]
Message-ID: <d928375478b1619690a5ac9269835f36@plan9.ucalgary.ca> (raw)

I'd like to have a comment from the 9p(2) man page clarified:

          In general, the File interface is appropriate for maintain-
          ing arbitrary file trees (as in ramfs). The File interface
          is best avoided when the tree structure is easily generated
          as necessary; this is true when the tree is highly struc-
          tured (as in cdfs and nntpfs) or is maintained elsewhere.

Is there a penalty associated with using the File interface?  It seems
to simplify greatly the implementation of 9p servers, so why should it
be avoided?

Say I have a server with static files that never change, should I use
File or roll my own Qid-handling routines a-la mntgen and friends?

thanks: andrey



             reply	other threads:[~2004-01-08 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 19:50 mirtchov [this message]
2004-01-09  0:37 ` Russ Cox

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=d928375478b1619690a5ac9269835f36@plan9.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).