From: "Larry Masinter" <masinter@parc.xerox.com> To: <jamsden@us.ibm.com>, <ietf-dav-versioning@w3.org> Cc: <brent.callaghan@eng.sun.com> Date: Sat, 9 Oct 1999 03:26:21 PDT Message-ID: <000801bf1240$bb1fe5e0$c3d2000d@copper.parc.xerox.com> In-Reply-To: <85256804.00049D6E.00@d54mta03.raleigh.ibm.com> Subject: RE: A question on Versioning-unaware clients # I admit, that they typically share the same files on a disk and thereby # share data, so you can 'put' with FTP and 'get' with HTTP, but that's not # the protocols interoperating, that's merely a shared disk. http and ftp 'interoperate' because their URL schemes were designed to allow possible substitution of the scheme name while leaving the rest of the URL alone. The design decision to try to align the URL schemes was intentional and discussed at length. It wasn't really very successful: the cases where it is possible to do the substitution are rare. If ftp didn't use the same hierarchical syntax as http, they wouldn't interoperate. Since WebDAV uses the same URL scheme as HTTP for its resources, it is reasonable to believe that FTP would continue to interoperate with WebDAV, if you 'put' with HTTP or webdav and 'get' with FTP. Whether or not ftp/webdav interoperability is "in scope" for the deltaV working group, it would be useful to at least note this issue as implementation advice. There was some hope that NFS (webnfs) and http would interoperate, too. A mapping between WebDAV and NFS v4 would be as interesting as the mapping with FTP. Larry -- http://www.parc.xerox.com/masinter