Re: [nfsv4] Minor Versioning.

Next message: Robert Gordon: "Re: [nfsv4] Minor Versioning."
Previous message: Robert Gordon: "[nfsv4] Minor Versioning."
In reply to: Robert Gordon: "[nfsv4] Minor Versioning."
Next in thread: Robert Gordon: "Re: [nfsv4] Minor Versioning."
Reply: Robert Gordon: "Re: [nfsv4] Minor Versioning."

trond.myklebust@fys.uio.no

Subject: Re: [nfsv4] Minor Versioning.
From: Trond Myklebust <trond.myklebust@fys.uio.no>
Date: Mon, 31 Jan 2005 16:21:17 -0800
Message-Id: <1107217277.16985.44.camel@lade.trondhjem.org>

må den 31.01.2005 Klokka 17:22 (-0600) skreiv Robert Gordon:
> I've been pondering the following :-
> 	 a server may advertise support for a minor version but may not
> 	(if the feature is classified as recommended) actually implement
> 	one (or any) of the 'minor version' features.
> 
> It has occurred to me that in 4.1 we should recommend a mechanism to
> query the server of it's capabilities and then make that mechanism
> mandatory in 4.2; This way it should be easy for a client to figure
> out if a server can handle sessions, pnfs etc...

Why is the existing NFS4ERR_NOTSUPP insufficient for these purposes?

Cheers,
  Trond

-- 
Trond Myklebust <trond.myklebust@fys.uio.no>

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4