From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <5b38ebbfff57fcd6da3f1cc282684bc4@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: device-specific qid.version behaviour (was Re: [9fans] QTCTL?)
Date: Mon,  5 Nov 2007 09:26:40 -0800
From: Skip Tavakkolian <9nut@9netics.com>
In-Reply-To: <7e65325a0cd907feca744c030f025319@quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: e992eff4-ead2-11e9-9d60-3106f5b1d025

> as i understand it you argue that qid.vers should change for each
> write for any server.  many devices just use 0 for qid.vers and never
> increment it.  so you can't use qid.vers on a stream or any fs
> that just sets qid.vers to 0.  so, in general, one can't use qid.vers
> as you propose.

it's supposed to change every time the file is modified.

i would think any mods would include the case where multiple
reads from the same file (e.g. ctl) at the same offset returns
new results.  but this would be excessive.

maybe 9p2010 Tread/Twrite could include the qid, which may be
supplied by the client (or left out).  if qid is supplied then the fs
has the option to enforce it; otherwise it works as it does now.