From owner-freebsd-arch Fri Mar 2 2:14:36 2001 Delivered-To: freebsd-arch@freebsd.org Received: from hand.dotat.at (sfo-gw.covalent.net [207.44.198.62]) by hub.freebsd.org (Postfix) with ESMTP id 189E137B720; Fri, 2 Mar 2001 02:14:32 -0800 (PST) (envelope-from fanf@dotat.at) Received: from fanf by hand.dotat.at with local (Exim 3.20 #3) id 14YmZ8-0000h8-00; Fri, 02 Mar 2001 10:13:38 +0000 Date: Fri, 2 Mar 2001 10:13:38 +0000 From: Tony Finch To: Terry Lambert Cc: Garrett Wollman , rwatson@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: Arch question for a UDF FS driver Message-ID: <20010302101338.B412@hand.dotat.at> References: <200103011420.JAA00305@khavrinen.lcs.mit.edu> <200103020335.UAA18058@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103020335.UAA18058@usr05.primenet.com> Organization: Covalent Technologies, Inc Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > >INRE: the use of the inode to generate entity id's: I'm not too >familiar with how they are used architecturally (only that they >exist); is there support for handling has collisions (e.g. the >id is treated as a hash instead of a uniqueid), or otherwise >changing the calculation used? This would seem to me to be a >big limitation in papches, allowing a single server to only >support MAX(ino_t) entities. The resource identified by a URL can be one of many entities, depending on the Accept-Language and Accept-Charset headers, etc. The Etag is used (by caches etc.) to distinguish between them. I think a limit of 2^64 entities isn't going to be a big problem. Tony. -- f.a.n.finch fanf@covalent.net dot@dotat.at THAMES DOVER: NORTH OR NORTHWEST 3 OR 4 VEERING NORTHEAST 5, OCCASIONALLY 6. OCCASIONAL SLEET. MODERATE OR GOOD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message