[5677] in www-talk@info.cern.ch

home help back first fref pref prev next nref lref last post

URLs for trees

daemon@ATHENA.MIT.EDU (Stephen Lewontin)
Sun Sep 18 00:43:29 1994

Date: Sun, 18 Sep 1994 06:33:49 +0200
Errors-To: listmaster@www0.cern.ch
Errors-To: listmaster@www0.cern.ch
Reply-To: stevel@osf.org
From: Stephen Lewontin <stevel@osf.org>
To: Multiple recipients of list <www-talk@www0.cern.ch>

> Latest suggestion (author requested anonymity):-
> 
> /...
> 
> 1) Its clean
> 2) Only backwards bongo is that anyone calling a directory ... will screw
> 	things.
> 3) It gets round semantic problems with *
> 
> 4) ITS COMPATIBLE WITH VMS !!!!
> 
> 
> >Groan, just as they finalised the draft :-)
> 
> Well the draft is hardly complete in any case. There are no URLs for posting
> news. And the gopher URL sucks turkey eggs. 
> 
> >I suppose it depends how you think about this facility. Are we talking
> >about a "meta object" (URL), or about an operation (method)? As we're
> >talking about protocol here I think the latter is more appropriate.
> 
> No we are talking about an operation. 
> 
> 
> fred/...  	is a directory listing (no client update, server update)
> fred/.../* 	is a compound object (lots of new software)

I've just come into the middle of this thread, so sorry if I'm missing
something, but /... happens to be the global root for DCE names. The
proposed use of /... would seem to be seriously incompatible.

Steve Lewontin/ Research Engineer/ OSF Research Institute.

home help back first fref pref prev next nref lref last post