traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Make the api of the _dispatch() method more concrete. I have no idea if 

this is the right way to document such things (Fred, help me out here :-),
but I got misled by the existing documentation and assumed the parameter
list was a *args sort of thing.
This commit is contained in:
Skip Montanaro 2004-09-03 00:04:05 +00:00
parent 15f611845b
commit 0bbf137fbd
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Doc/lib/libsimplexmlrpc.tex
View File

@ -59,8 +59,13 @@ simple, stand alone XML-RPC servers.
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
with the requested method name and the parameters from the request;
the return value is returned to the client as the result. If
with the requested method name and the parameters from the request. Its
API is \code{def \method{_dispatch}(self, method, params)} (note tha
\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
\var{instance} does not have a \method{_dispatch()} method, it is
searched for an attribute matching the name of the requested method;
if the requested method name contains periods, each component of the