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

Re: Comments please!

From: Joe Orton <joe@orton.demon.co.uk>
Date: Tue, 25 Jan 2000 11:19:58 +0000
To: w3c-dist-auth@w3.org
Message-ID: <20000125111958.A25078@york.ac.uk>
> Hmm. But this doesn't solve my problem. Let's say that my website is called
> 'http://www.foo.com'. If I do a
> get on this url, I'll get 'http://www.foo.com/index.htm' by default. But
> 'http://www.foo.com' is also a directory at the to level. So if a user types
> 'http://www.foo.com' I don't know if I should perform a Get or a Propfind,
> both are valid. The user types the same thing for directory browsing in
> 'http://www.foo.com' and for getting the default page.

I think this mostly a UI problem. From the user's point of view, have two "views" 
on a collection resource; it's GET response, and the listing of collection members
from a PROPFIND response. These correspond to the traditional "web browser" mode of
operation, and the traditional "file browser/explorer" mode of operation.

Like you say, in Web Folders you have the "Open as Web folder" checkbox on open
dialog, which selects which of these views should be used for the given URI. 
Another way to do this (maybe Web Folders does this too, I've not been that side of
the fence for a while?), is to have some way of switching between modes from within
the browser; a toolbar button, or a drop-down box, or whatever.

So then, the user can browse about their web site, happily viewing their pages,
then maybe they want to move some files about, so they hit the "view collection
contents" button, and they can do that, then switch back again when they've
finished. That would be a nice interface, IMO.

Received on Tuesday, 25 January 2000 06:20:39 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:21 UTC