Re: Proposed NFS URL scheme

Markus Stumpf (maex@leo.org)
Wed, 6 Nov 1996 12:41:30 +0100


Subject: Re: Proposed NFS URL scheme
To: masinter@parc.xerox.com (Larry Masinter)
Date: 	Wed, 6 Nov 1996 12:41:30 +0100
Cc: uri@bunyip.com
In-Reply-To: <96Nov2.185252pst."2757"@golden.parc.xerox.com> from "Larry Masinter" at Nov 3, 96 03:52:52 am
From: maex@leo.org (Markus Stumpf)
Message-Id: <96Nov6.124143mesz.21092@hprbg5.informatik.tu-muenchen.de>

Sorry if this is too offtopic, but I've been reading this and related
lists not too closely, but with Larry's mailing and the NFS topic I thought
I might jump in :-)

I am working on a project right now which would have some additional
needs in URLs which might be worth a thought (I hope).

We are working on a distributed archive (like FTP archives) with some
of the information replicated (e.g. through mirrors). A config file
(currently) holds all the information need to build a view of the archive.
Some of the information is provided via NFS, but as it is not useful
(IMHO) to mount this over distant network connections there are
restrictions in the exports of those filesystems.
While we are trying to make some weighting on the quality of the
intended mountpoint the exporteur might disagree. It would be much easier
not to use a "try and error" method, but to have a way to (optionally) specify
restriction of access permissions within an URL.
This might be as easy as e.g. access=password (to indicate that a passwd
is needed to access the information) or access=*.net,*.com (for hostname
masking) ...

Is this something that should/could go into URLs?

Thanks for listening

	\Maex
-- 
______________________________________________________________________________
 Markus Stumpf              maex@leo.org            http://www.leo.org/~maex/