WebNFS Client SDK
FCS 1.1 Release Notes
Version Notes
This release is version 1.1 and has been tested using JDK1.1.6.
Release Contents
This release includes the following:
- NFS Classes
- Extended Filesystem API Classes
- Sample Code
- Documentation including:
New Features and Changes
- WebNFS XFileAccessor Interface Reference
- Additional Methods in XFile
- A flush() method has been added to XFileOutputStream and
XRandomAccessFile. This method allows buffered data to
be written to a device without requiring the file be closed.
- A getAccessor() method was added to XFile. This method
allows implementations of XFileAccessor to refer to
the underlying accessor instance of another accessor.
This method was required by the implementation and must
be public because XFileAccessor classes are not part of
the com.sun.xfile package.
- Reference to XFileExtensionAccessor
The new package architecture supports loadable accessors
that are not part of the com.sun.xfile package. Each
Accessor and ExtensionAccessor lives in its own package
named with the scheme name, e.g.
com.sun.nfs.XFileAccessor
com.sun.nfs.XFileExtensionAccessor
This is the new generic way to access
all XFileExtensionAccessors. In WebNFS SDK 1.0, the ExtensionAccessor for
nfs was referred to as the nfsXFileExtensionAccessor.
The new name for this class (as for all such classes) is just
"XFileExtensionAccessor" and made uniqued by the class prefix.
Hence the NFS XFileExtensionAccessor is now known as:
com.sun.nfs.XFileExtensionAccessor
For backwards compatibility, there will be
a stub class "nfsXFileExtensionAccessor"
within the com.sun.xfile package. Thus, nfsXFileExtensionAccessor
has been deprecated.
- Reference to native files
The WebNFS SDK 1.0 documentation made references to a "native" accessor
equivalent to other accessors. Any filename that could not
be evaluated as a URL was a assumed to be a local file.
We implemented a "native" access as another loadable
accessor which is referred to as file XFileAccessor.
The pathname dependent methods of "native" are handled within XFile and the
"file" accessor implements only the I/O methods.
Known Problems/Issues
Following is a list of known problems or issues.
4123748: Client code doesn't escape "%" when evaluating relative URL
4155312: Spurious retransmissions from Windows/NT
4155313: Threads writing to common XFileOutputStream sometimes hang
This version of the SDK has been tested in 1.1.6 and will not compile or
run with the beta version of JDK 1.2. However, future releases of the
SDK will be compliant to the FCS version of JDK 1.2.
The WebNFS Server
You should test your client application against both WebNFS-enabled servers
and non-WebNFS-enabled servers. Currently 3 commercial
WebNFS-enabled servers are available:
- the Solaris 2.6 or later release from Sun
- the AIX 4.2.1 release from IBM
- the Interdrive NFS for NT 2.0 from FTP Software
WebNFS client applications should assume that the server is WebNFS enabled.
Please refer to the WebNFS
Client Specification (RFC2054), section 7 "Contacting the Server" for
details on recommended coding techniques.
However, if you do not have access to a WebNFS enabled server, your
application should still work. The WebNFS client code falls back to what
the server supports.
Last modified: July 28, 1998
Copyright 1994-1998 Sun Microsystems, Inc. 901 San Antonio Road,
Palo Alto, CA 94303 USA. All Rights Reserved.