From: shepler@eng.sun.com
Date: 07/20/99-12:17:39 PM Z
From: shepler@eng.sun.com Message-ID: <3794AF33.D1E3A6C9@eng.sun.com> Date: Tue, 20 Jul 1999 12:17:39 -0500 Subject: Re: compound request/reply jstarng@us.ibm.com wrote: > > For V2 and V3 NFS protocols, one request/reply resides in one RPC. > If encoding/decoding failed, the request failed with encoding/decoding failure > return code. > > For V4 NFS protocol, one RPC contains many requests/replies. > For example, there exists 8 requests in one RPC request: > req1, req2, req3, req4, req5, req6, req7 and req8. > From req1 to req4 are decoded successfully, but req5 failed to be decoded. > What should we do about it? Should we fail the complete RPC request? > Or should we still accept from req1 to req4? How do we reply the error > to client? Since decoding error resides in RPC header, not part of NFS > error return code. > > The similar condition applies to replies. > For example, there exists 8 replies ready for one RPC request: > rep1, rep2, rep3, rep4, rep5, rep6, rep7 and rep8. > From rep1 to rep4 are encoded successfully, but rep5 failed to be encoded. > What should we do about it? Should we fail the complete RPC request? > Or should we still reply from rep1 to rep4? How do we reply the error > to client? Since encoding error resides in RPC header, not part of NFS > error return code. As you point out, the errors are at two different levels (RPC and NFS). Encode and decode errors are RPC errors and if either of them occur then the entire RPC request (COMPOUND request in this case) fails. Spencer
This archive was generated by hypermail 2.1.2 : 03/04/05-01:47:22 AM Z CST