Patch #469517: Info about rpcgen compilers.
This commit is contained in:
parent
875eeaa193
commit
401a76dcab
|
@ -23,3 +23,9 @@ Other clients are tested similarly.
|
|||
|
||||
For hostname, use e.g. wuarchive.wustl.edu or gatekeeper.dec.com (two
|
||||
hosts that are known to export NFS filesystems with little restrictions).
|
||||
|
||||
There are now two different RPC compilers:
|
||||
|
||||
1) Wim Lewis rpcgen.py found on http://www.omnigroup.com/~wiml/soft/stale-index.html#python.
|
||||
|
||||
2) Peter Åstrands rpcgen.py, which is part of "pynfs" (http://www.cendio.se/~peter/pynfs/).
|
||||
|
|
|
@ -1,11 +1,12 @@
|
|||
# Mount RPC client -- RFC 1094 (NFS), Appendix A
|
||||
|
||||
# This module demonstrates how to write your own RPC client in Python.
|
||||
# Since there is no RPC compiler for Python (yet), you must first
|
||||
# create classes derived from Packer and Unpacker to handle the data
|
||||
# types for the server you want to interface to. You then write the
|
||||
# client class. If you want to support both the TCP and the UDP
|
||||
# version of a protocol, use multiple inheritance as shown below.
|
||||
# When this example was written, there was no RPC compiler for
|
||||
# Python. Without such a compiler, you must first create classes
|
||||
# derived from Packer and Unpacker to handle the data types for the
|
||||
# server you want to interface to. You then write the client class.
|
||||
# If you want to support both the TCP and the UDP version of a
|
||||
# protocol, use multiple inheritance as shown below.
|
||||
|
||||
|
||||
import rpc
|
||||
|
|
Loading…
Reference in New Issue