RE: [nfsv4] personal drafts of interest to NFSv4 WG

Next message: Khan, Saadia: "[nfsv4] ACE4_TRAVERSE permissions"
Previous message: Noveck, Dave: "RE: [nfsv4] personal drafts of interest to NFSv4 WG"
In reply to: Noveck, Dave: "RE: [nfsv4] personal drafts of interest to NFSv4 WG"

trond.myklebust@fys.uio.no

Subject: RE: [nfsv4] personal drafts of interest to NFSv4 WG
From: Trond Myklebust <trond.myklebust@fys.uio.no>
Date: Fri, 18 Feb 2005 20:38:43 -0500
Message-Id: <1108777123.10027.44.camel@lade.trondhjem.org>

fr den 18.02.2005 Klokka 16:17 (-0500) skreiv Noveck, Dave:

> You could create new versions of a large number of operations and
> add stateids or clientids to them, but this seems ugly especially as
> as these would not be needed once sessions were adopted.

I've advocated the concept of a "current stateid" that acts in the same
way as the "current filehandle" several times before on this list. If we
add an operation that acts like PUTFH in order to say "use this stateid
in order to validate the next operation", we do not have to modify
READDIR.

The concept of a current stateid is something that we have discussed
anyway in order to do complex stateful operations such as OPEN+LOCK+READ
+LOCKU+CLOSE in a single compound.

Cheers,
  Trond

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

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