Class Nfs3ReadlinkResponse
This method reads the data associated with a symbolic link. The data is an ASCII string that is opaque to the server. That is, whether created by the NFS version 3 protocol software from a client or created locally on the server, the data in a symbolic link is not interpreted when created, but is simply stored.
A symbolic link is nominally a pointer to another file. The data is not necessarily interpreted by the server, just stored in the file. It is possible for a client implementation to store a path name that is not meaningful to the server operating system in a symbolic link. A READLINK operation returns the data to the client for interpretation. If different implementations want to share access to symbolic links, then they must agree on the interpretation of the data in the symbolic link.
-
Field Summary
Fields inherited from class RpcResponse
_xid -
Constructor Summary
ConstructorsConstructorDescriptionCreates the response, as specified by RFC 1813 (https://tools.ietf.org/html/rfc1813). -
Method Summary
Methods inherited from class NfsReadlinkResponse
getData, unmarshallingMethods inherited from class NfsResponseBase
getAttributes, getFileHandle, getState, makeNfsGetAttributes, makeNfsGetAttributes, stateIsOk, toString, unmarshallingAttributes, unmarshallingAttributes, unmarshallingFileHandle, unmarshallingFileHandleMethods inherited from class RpcResponse
getAcceptStatus, getDirection, getRejectStatus, getReplyStatus, getXid
-
Constructor Details
-
Nfs3ReadlinkResponse
public Nfs3ReadlinkResponse()Creates the response, as specified by RFC 1813 (https://tools.ietf.org/html/rfc1813).This method reads the data associated with a symbolic link. The data is an ASCII string that is opaque to the server. That is, whether created by the NFS version 3 protocol software from a client or created locally on the server, the data in a symbolic link is not interpreted when created, but is simply stored.
A symbolic link is nominally a pointer to another file. The data is not necessarily interpreted by the server, just stored in the file. It is possible for a client implementation to store a path name that is not meaningful to the server operating system in a symbolic link. A READLINK operation returns the data to the client for interpretation. If different implementations want to share access to symbolic links, then they must agree on the interpretation of the data in the symbolic link.
-