WebNFS is not implemented yet :-( (-> what about Necko ?) (Question: Where can I suggest such features ? I id not found such a page :-( )

For such discussions use news://news.mozilla.org/netscape.public.mozilla.netlib

verified

Changing all Networking Library/Browser bugs to Networking-Core component for Browser. Occasionally, Bugzilla will burp and cause Verified bugs to reopen when I do this in a bulk change. If this happens, I will fix. ;-)

I found a way to implement nfs:-URLs in a __simple__ way on the Solaris (>= 2.6) platform. In Solaris 7 (AFAIK Solaris 2.6 has the same feature) the /net directory is served by the automounter. Any access to /net/www.yahoo.de/home/terror/killThePresident.txt accesses the file "/home/terror/killThePresident.txt" via NFS on the server www.yahoo.de The NFS-URL can then be implemented using the following trick: nfs://<name-of-server>/<path> is mapped to file:///net/<name-of-server>/<path> easy, isn't it ?? In the SUNWebnfs package I found a couple of links to the (Web-)NFS protocol: -- snip -- Version 2 and version 3 of the NFS protocol are described in RFC 1094 (version 2) and RFC 1813 (version 3). The WebNFS method of binding to the server is described in RFC 2054 (client side) and RFC 2055 (server side). The NFS URL scheme is specified in RFC 2224. The X/Open Specification for NFS including descriptions of the MOUNT protocol and Network Lock Manager protocol can be ordered from The Open Group. If you are interested in comparing the performance of NFS servers from various vendors, take a look at the SPEC SFS Suite benchmark. NFS vendors also test their client and server implementations for interoperability at Connectathon. For information on the administration of NFS on Solaris clients and servers, check the NFS Administration Guide. If you would like to communicate with other NFS users, administrators, or developers, try the Newsgroup comp.protocols.nfs. -- snip --

Who is the owner if the "necko" module ? I'd like to write a "mini"-implemenations using the Solaris NFS API...

Bulk move of all Networking-Core (to be deleted component) bugs to new Networking component.

this isn't fixed...

there is a workaround, so WFM

REOPEN: nfs: is not the same as just getting file: access mapped to mount points. -> future, set to defaults. fixed URL to make it the RFC. I don't think anyone will ever do this, but at least in this form, it will trap dupes.

.