Re: client local file system access issues

• Mail folder: WWW Talk Jan 94-present
• Next message: Frederick G.M. Roeber: "Re: Server control over history?"
• Previous message: Daniel W. Connolly: "Re: Server control over history? "
• Maybe in reply to: Kevin Altis: "client local file system access issues"

Errors-To: listmaster@www0.cern.ch
Date: Tue, 15 Feb 1994 16:55:36 --100
Message-id: <9402151551.AA01157@void.ncsa.uiuc.edu>
Errors-To: listmaster@www0.cern.ch
Reply-To: atotic@ncsa.uiuc.edu
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: atotic@ncsa.uiuc.edu (Alexsander Totic)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: client local file system access issues
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 805

> Mac Mosaic does file:///drive name/path Spaces are okay at least in the
> drive name.

MacMosaic actually accepts:

file://atotic1.ncsa.uiuc.edu/AlexWork/Test files/main.html
file://localhost/AlexWork/Test files/main.html
file:///AlexWork/Test files/main.html

as valid paths for the local file. There are certain problems with using / in
your names, but other than that, I think its local file handling is
completer.

> file or handing it off to an external browser. So, the case of
> file://localhost should be treated special be the client so that it just
> goes and used the local file. You won't have to wait for a 14MB audio/video
> file to get copied to a different directory before the external mpeg player
> launches to play the file.

Yeah, we just have not gotten around to doing it.

Aleks