9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] synthetic filesystems and changing data
Date: Thu,  9 Aug 2007 21:57:34 -0400	[thread overview]
Message-ID: <f22c91a2af42dfcff1289087f933635b@coraid.com> (raw)
In-Reply-To: <46BBC396.9040009@ec.gc.ca>

why not just tie the fid to a "file" version.  then it would be easy
to handle offsets.

- erik

On Thu Aug  9 21:47:02 EDT 2007, John.Marshall@ec.gc.ca wrote:
> Hi,
> 
> I am trying to understand the general practice, under
> Plan 9, for synthetic filesystems for serving up a "file"
> which:
> 1) returns data that changes (quickly), and
> 2) returns data whose size is larger than the message
>     size agreed upon at *version interchange.
> 
> Practically, what I am wondering is:
> 1) what to do when the "file" content changes between
>     multiple *read operations (assuming that the reads
>     are done quickly)? Is it just tough luck for the client?
> 2) whether or not synthetic filesystems generally handle
>     (or not) the offset parameter? I imagine to do this
>     requires relatively static content, is difficult, or
>     there is an assumption that the size of the content
>     _must_ fit in the message.
> 
> Thanks,
> John
> 


  reply	other threads:[~2007-08-10  1:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10  1:47 John Marshall
2007-08-10  1:57 ` erik quanstrom [this message]
2007-08-10  8:13   ` Charles Forsyth
2007-08-10  9:40     ` maht
2007-08-10  6:49 ` matt
2007-08-10 12:32   ` John Marshall
2007-08-10 15:13     ` Kris Maglione
2007-08-10 15:47       ` nemo

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=f22c91a2af42dfcff1289087f933635b@coraid.com \
    --to=quanstro@coraid.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).