From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <46BBC396.9040009@ec.gc.ca>
Date: Thu,  9 Aug 2007 21:47:02 -0400
From: John Marshall <John.Marshall@ec.gc.ca>
User-Agent: Thunderbird 2.0.0.6 (X11/20070728)
MIME-Version: 1.0
To: 9fans@cse.psu.edu
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [9fans] synthetic filesystems and changing data
Topicbox-Message-UUID: a2c33eb2-ead2-11e9-9d60-3106f5b1d025

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