libsimplexmlrpc.tex 8.78 KB
Newer Older
1 2 3 4
\section{\module{SimpleXMLRPCServer} ---
         Basic XML-RPC server}

\declaremodule{standard}{SimpleXMLRPCServer}
5
\modulesynopsis{Basic XML-RPC server implementation.}
6 7 8
\moduleauthor{Brian Quinlan}{brianq@activestate.com}
\sectionauthor{Fred L. Drake, Jr.}{fdrake@acm.org}

9
\versionadded{2.2}
10 11

The \module{SimpleXMLRPCServer} module provides a basic server
12 13 14
framework for XML-RPC servers written in Python.  Servers can either
be free standing, using \class{SimpleXMLRPCServer}, or embedded in a
CGI environment, using \class{CGIXMLRPCRequestHandler}.
15 16

\begin{classdesc}{SimpleXMLRPCServer}{addr\optional{,
17
                                      requestHandler\optional{,
Gregory P. Smith's avatar
Gregory P. Smith committed
18
					logRequests\optional{, allow_none\optional{, encoding}}}}}
19

20 21 22
  Create a new server instance.  This class
  provides methods for registration of functions that can be called by
  the XML-RPC protocol.  The \var{requestHandler} parameter
23 24 25 26 27
  should be a factory for request handler instances; it defaults to
  \class{SimpleXMLRPCRequestHandler}.  The \var{addr} and
  \var{requestHandler} parameters are passed to the
  \class{\refmodule{SocketServer}.TCPServer} constructor.  If
  \var{logRequests} is true (the default), requests will be logged;
28 29 30 31 32
  setting this parameter to false will turn off logging.  
  The \var{allow_none} and \var{encoding} parameters are passed on to 
  \module{xmlrpclib} and control the XML-RPC responses that will be returned 
  from the server.
  \versionchanged[The \var{allow_none} and \var{encoding} parameters were added]{2.5}
33 34
\end{classdesc}

35
\begin{classdesc}{CGIXMLRPCRequestHandler}{\optional{allow_none\optional{, encoding}}}
36
  Create a new instance to handle XML-RPC requests in a CGI
37 38 39 40 41 42
  environment. 
  The \var{allow_none} and \var{encoding} parameters are passed on to 
  \module{xmlrpclib} and control the XML-RPC responses that will be returned 
  from the server.
  \versionadded{2.3}
  \versionchanged[The \var{allow_none} and \var{encoding} parameters were added]{2.5}
43
\end{classdesc}
44 45 46 47 48 49 50 51 52 53 54

\begin{classdesc}{SimpleXMLRPCRequestHandler}{}
  Create a new request handler instance.  This request handler
  supports \code{POST} requests and modifies logging so that the
  \var{logRequests} parameter to the \class{SimpleXMLRPCServer}
  constructor parameter is honored.
\end{classdesc}


\subsection{SimpleXMLRPCServer Objects \label{simple-xmlrpc-servers}}

55 56 57
The \class{SimpleXMLRPCServer} class is based on
\class{SocketServer.TCPServer} and provides a means of creating
simple, stand alone XML-RPC servers.
58 59 60

\begin{methoddesc}[SimpleXMLRPCServer]{register_function}{function\optional{,
                                                          name}}
61 62 63 64 65 66
  Register a function that can respond to XML-RPC requests.  If
  \var{name} is given, it will be the method name associated with
  \var{function}, otherwise \code{\var{function}.__name__} will be
  used.  \var{name} can be either a normal or Unicode string, and may
  contain characters not legal in Python identifiers, including the
  period character.
67 68
\end{methoddesc}

69 70
\begin{methoddesc}[SimpleXMLRPCServer]{register_instance}{instance\optional{,
                                       allow_dotted_names}}
71 72 73
  Register an object which is used to expose method names which have
  not been registered using \method{register_function()}.  If
  \var{instance} contains a \method{_dispatch()} method, it is called
74
  with the requested method name and the parameters from the request.  Its
75
  API is \code{def \method{_dispatch}(self, method, params)} (note that
76 77 78 79 80
  \var{params} does not represent a variable argument list).  If it calls an
  underlying function to perform its task, that function is called as
  \code{func(*params)}, expanding the parameter list.
  The return value from \method{_dispatch()} is returned to the client as
  the result.  If
81
  \var{instance} does not have a \method{_dispatch()} method, it is
82 83 84 85
  searched for an attribute matching the name of the requested method.

  If the optional \var{allow_dotted_names} argument is true and the
  instance does not have a \method{_dispatch()} method, then
86 87 88 89 90
  if the requested method name contains periods, each component of the
  method name is searched for individually, with the effect that a
  simple hierarchical search is performed.  The value found from this
  search is then called with the parameters from the request, and the
  return value is passed back to the client.
91 92 93 94 95 96 97 98 99 100 101

  \begin{notice}[warning]
  Enabling the \var{allow_dotted_names} option allows intruders to access
  your module's global variables and may allow intruders to execute
  arbitrary code on your machine.  Only use this option on a secure,
  closed network.
  \end{notice}

  \versionchanged[\var{allow_dotted_names} was added to plug a security hole;
  prior versions are insecure]{2.3.5, 2.4.1}

102
\end{methoddesc}
103 104 105 106 107 108 109 110 111 112 113

\begin{methoddesc}{register_introspection_functions}{}
  Registers the XML-RPC introspection functions \code{system.listMethods},
  \code{system.methodHelp} and \code{system.methodSignature}. 
  \versionadded{2.3}
\end{methoddesc}

\begin{methoddesc}{register_multicall_functions}{}
  Registers the XML-RPC multicall function system.multicall.
\end{methoddesc}

Andrew M. Kuchling's avatar
Andrew M. Kuchling committed
114 115 116 117 118 119 120 121 122
\begin{memberdesc}[SimpleXMLRPCServer]{rpc_paths}
An attribute value that must be a tuple listing valid path portions of
the URL for receiving XML-RPC requests.  Requests posted to other
paths will result in a 404 ``no such page'' HTTP error.  If this
tuple is empty, all paths will be considered valid.
The default value is \code{('/', '/RPC2')}.
  \versionadded{2.5}
\end{memberdesc}

123 124 125
Example:

\begin{verbatim}
126
from SimpleXMLRPCServer import SimpleXMLRPCServer
127

128
# Create server
129 130
server = SimpleXMLRPCServer(("localhost", 8000))
server.register_introspection_functions()
131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146

# Register pow() function; this will use the value of 
# pow.__name__ as the name, which is just 'pow'.
server.register_function(pow)

# Register a function under a different name
def adder_function(x,y):
    return x + y
server.register_function(adder_function, 'add')

# Register an instance; all the methods of the instance are 
# published as XML-RPC methods (in this case, just 'div').
class MyFuncs:
    def div(self, x, y): 
        return x // y
    
147
server.register_instance(MyFuncs())
148 149

# Run the server's main loop
150 151 152
server.serve_forever()
\end{verbatim}

153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168
The following client code will call the methods made available by 
the preceding server:

\begin{verbatim}
import xmlrpclib

s = xmlrpclib.Server('http://localhost:8000')
print s.pow(2,3)  # Returns 2**3 = 8
print s.add(2,3)  # Returns 5
print s.div(5,2)  # Returns 5//2 = 2

# Print list of available methods
print s.system.listMethods()
\end{verbatim}


169 170 171 172 173 174 175
\subsection{CGIXMLRPCRequestHandler}

The \class{CGIXMLRPCRequestHandler} class can be used to 
handle XML-RPC requests sent to Python CGI scripts.

\begin{methoddesc}{register_function}{function\optional{, name}}
Register a function that can respond to XML-RPC requests. If 
176
\var{name} is given, it will be the method name associated with 
177 178 179 180 181 182 183 184 185 186 187 188
function, otherwise \var{function.__name__} will be used. \var{name}
can be either a normal or Unicode string, and may contain 
characters not legal in Python identifiers, including the period
character. 
\end{methoddesc}

\begin{methoddesc}{register_instance}{instance}
Register an object which is used to expose method names 
which have not been registered using \method{register_function()}. If 
instance contains a \method{_dispatch()} method, it is called with the 
requested method name and the parameters from the 
request; the return value is returned to the client as the result.
189
If instance does not have a \method{_dispatch()} method, it is searched 
190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218
for an attribute matching the name of the requested method; if 
the requested method name contains periods, each 
component of the method name is searched for individually, 
with the effect that a simple hierarchical search is performed. 
The value found from this search is then called with the 
parameters from the request, and the return value is passed 
back to the client. 
\end{methoddesc}

\begin{methoddesc}{register_introspection_functions}{}
Register the XML-RPC introspection functions 
\code{system.listMethods}, \code{system.methodHelp} and 
\code{system.methodSignature}.
\end{methoddesc}

\begin{methoddesc}{register_multicall_functions}{}
Register the XML-RPC multicall function \code{system.multicall}.
\end{methoddesc}

\begin{methoddesc}{handle_request}{\optional{request_text = None}}
Handle a XML-RPC request. If \var{request_text} is given, it 
should be the POST data provided by the HTTP server, 
otherwise the contents of stdin will be used.
\end{methoddesc}

Example:

\begin{verbatim}
class MyFuncs:
219
    def div(self, x, y) : return x // y
220 221 222 223 224 225 226 227


handler = CGIXMLRPCRequestHandler()
handler.register_function(pow)
handler.register_function(lambda x,y: x+y, 'add')
handler.register_introspection_functions()
handler.register_instance(MyFuncs())
handler.handle_request()
228
\end{verbatim}