From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@labs.coraid.com>
Date: Fri, 29 Oct 2010 13:16:33 -0400
To: 9fans@9fans.net
Message-ID: <5e8c3d0ee7c2cdd8d02371de034918ad@coraid.com>
In-Reply-To: <AANLkTikQOe2Q_0aExBTtv83UdgD5v28jD0eWD-qk=kiR@mail.gmail.com>
References: <AANLkTinAnAA6+ky9qn29tuAqjTx2SUmVW258CRzoN4B=@mail.gmail.com>
	<6b21211797cc4b5ff93802313f2fd94c@terzarima.net>
	<AANLkTingY5En8LZe1s5YcCHObdyjJ3+v6gf7sv8ds0ov@mail.gmail.com>
	<AANLkTinuQg11-vW0iSXhXObkNhsBSFR1nTBqpzJhekGk@mail.gmail.com>
	<AANLkTikQOe2Q_0aExBTtv83UdgD5v28jD0eWD-qk=kiR@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] A little more ado about async Tclunk
Topicbox-Message-UUID: 7246dc54-ead6-11e9-9d60-3106f5b1d025

> I've been using 'decent' in much the same way 'standard' or 'disk' is being
> used; I'd actually prefer nemo's idea of a QTDECENT qidtype to marking the
> file server. The original QTDECENT proposal (actually originally inverted
> logic, in the form of QTCTL) said this about indecent files: "this file does
> not behave like a regular file, do not cache and handle with care".

unfortunately, unless you are talking about archival storage (e.g., /n/dump),
i think the difference between a "decent" file and a ctl file starts to seem slippery.
unless a file is exclusive open it's hard to be sure that a file won't change
underneath you.

- erik