W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 1999

RE: I-D ACTION:draft-hopmann-collection-props-00.txt

From: Lisa Lippert (Dusseault) (Exchange) <lisal@exchange.microsoft.com>
Date: Mon, 11 Jan 1999 13:23:16 -0800
Message-ID: <BFF90FB6CF66D111BF4F0000F840DB8506062460@LASSIE>
To: "'John Stracke'" <francis@netscape.com>
Cc: "'w3c-dist-auth@w3.org'" <w3c-dist-auth@w3.org>
I just noticed the possibility for infinite loops today.  That would be
fixed by requiring the "defaultdocument" property to point to a member of
the collection.  Perhaps we should also say that "defaultdocument" cannot
point to a collection, which could in turn point somewhere else...

Lisa

-----Original Message-----
From: John Stracke [mailto:francis@netscape.com]
Sent: Monday, January 11, 1999 1:13 PM
To: w3c-dist-auth@w3.org
Subject: Re: I-D ACTION:draft-hopmann-collection-props-00.txt


"Lisa Lippert (Dusseault) (Exchange)" wrote:

> Three: Two new features in this draft that work together are the
> "defaultdocument" property

I kind of like defaultdocument, but I think it might need to be a list.
Most
existing servers have a rule for picking out the default document (e.g.,
"index.html, then index.cgi, then index.txt"); it would be a Good Thing if,
on
directories with no default set, they could expose the rule rather than just
the document that they would currently serve up.

(I'm not sure whether there's a need to be able to *set* an individual
collection's defaultdocument to a list, but it could be useful, e.g., if a
server decides that defaultdocument should be inherited by subcollections.)

Also, one oversight (probably): the current Draft does not require that
defaultdocument point to a member of the collection; as it stands now, it
would
be possible for it to point to a completely separate server.  This might be
a
cute trick occasionally, but I think it'd be cleaner to create a referential
member and make that the default.

Oh, and the Draft does not specify what "the default document for a
collection"
means.  We all know that it's the resource that gets referenced by a GET or
HEAD on the collection URI; but that should be specified.

--
/====================================================================\
|John (Francis) Stracke    |My opinions are my own.|S/MIME supported |
|Software Retrophrenologist|=========================================|
|Netscape Comm. Corp.      |Q: What goes "Pieces of 7! Pieces of 7!"?|
|francis@netscape.com      |A: A parroty error!!                     |
\====================================================================/
Received on Monday, 11 January 1999 16:27:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:49 GMT