From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8536106e05d2ec2c9996c2d623575b2c@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] qids
From: rog@vitanuova.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Wed, 26 Mar 2003 17:42:54 +0000
Topicbox-Message-UUID: 851f6f5e-eacb-11e9-9e20-41e7f4b1d025

> Servers of original files are encouraged to use only the low 48 bits
> of the qid.path to permit encapsulating servers to use the top 16 bits
> to generate uniqueness.

what about those that encapsulate the encapsulators?

i don't see how this helps much, given that you can't rely
on it. i suppose it reduces the likelyhood that an exportfs-like
service will have to rewrite a file's qid when it's walked to,
and more so if the encapsulating service chooses a random
starting point for those top 16 bits... is that the point?

  rog.