From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Wed,  5 Dec 2012 07:39:36 -0500
To: 9fans@9fans.net
Message-ID: <aa13663635c2e804960036d64919dd7e@brasstown.quanstro.net>
In-Reply-To: <CAOw7k5hCyZAZxZQaeLZAMh8R62qQPpcWC_aWf2Og4HPrU=h6OA@mail.gmail.com>
References: <af3d20ce-0b0c-45c5-b657-6ac5910ad865@googlegroups.com>
	<CAOw7k5h1PPpjqP+KJWC+zbdOZ2OPhWe=aG-SEdV9cfSC+5pPrQ@mail.gmail.com>
	<CAOw7k5hCyZAZxZQaeLZAMh8R62qQPpcWC_aWf2Og4HPrU=h6OA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] QTEXCL/DMEXCL redundancy
Topicbox-Message-UUID: f08fb3be-ead7-11e9-9d60-3106f5b1d025

On Wed Dec  5 06:03:50 EST 2012, charles.forsyth@gmail.com wrote:
> The reason for having those bits in the qid.type is because the qid is
> returned on open, allowing (say) caching programs to discover
> directory/not append-only/not and other details without needing
> another transaction (and a race) to stat the file.
>

i couldn't find a single program that takes advantage of this.

- erik