From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: device-specific qid.version behaviour (was Re: [9fans] QTCTL?) Date: Mon, 5 Nov 2007 14:12:13 -0800 From: Skip Tavakkolian <9nut@9netics.com> In-Reply-To: <872562cb6911793f3b35fc3c03bb98b6@9netics.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: eabd3682-ead2-11e9-9d60-3106f5b1d025 >>> 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. simpler yet, a flag to open that would tell the fs it should strictly enforce the change notice by returning an error for a subsequent read if the file was changed after the open.