- From: Markus Stumpf <maex@leo.org>
- Date: Wed, 6 Nov 1996 12:41:30 +0100
- To: masinter@parc.xerox.com (Larry Masinter)
- Cc: uri@bunyip.com
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/
Received on Wednesday, 6 November 1996 06:49:42 UTC