Lines Matching refs:XML

1 :mod:`xmlrpclib` --- XML-RPC client access
5    :synopsis: XML-RPC client access.
24 XML-RPC is a Remote Procedure Call method that uses XML passed via HTTP(S) as a
27 supports writing XML-RPC client code; it handles all the details of translating
28 between conformable Python objects and XML on the wire.
45    remote XML-RPC server.  The required first argument is a URI (Uniform Resource
54    XML; the default behaviour is for ``None`` to raise a :exc:`TypeError`. This is
55    a commonly-used extension to the XML-RPC specification, but isn't supported by
66    the remote server as part of the connection process when invoking an XML-RPC
78    Types that are conformable (e.g. that can be marshalled through XML),
85    | XML-RPC type         | Python type                                           |
115    This is the full set of data types supported by XML-RPC.  Method calls may also
116    raise a special :exc:`Fault` instance, used to signal XML-RPC server errors, or
123    When passing strings, characters special to XML such as ``<``, ``>``, and ``&``
125    ensure that the string is free of characters that aren't allowed in XML, such as
127    tab, newline and carriage return); failing to do this will result in an XML-RPC
128    request that isn't well-formed XML.  If you have to pass arbitrary strings via
129    XML-RPC, use the :class:`Binary` wrapper class described below.
148    `XML-RPC HOWTO <http://www.tldp.org/HOWTO/XML-RPC-HOWTO/index.html>`_
149       A good description of XML-RPC operation and client software in several languages.
150       Contains pretty much everything an XML-RPC client developer needs to know.
152    `XML-RPC Introspection <http://xmlrpc-c.sourceforge.net/introspection.html>`_
153       Describes the XML-RPC protocol extension for introspection.
155    `XML-RPC Specification <http://www.xmlrpc.com/spec>`_
158    `Unofficial XML-RPC Errata <http://effbot.org/zone/xmlrpc-errata.htm>`_
160       details in the XML-RPC specification, as well as hint at
161       'best practices' to use when designing your own XML-RPC
170 procedure call accepted by the XML-RPC server.  Calling the method performs an
176 Servers that support the XML introspection API support some common methods
183    supported by the XML-RPC server.
188    This method takes one parameter, the name of a method implemented by the XML-RPC
208    This method takes one parameter, the name of a method implemented by the XML-RPC
230    Write the XML-RPC encoding of this Boolean item to the out stream object.
273       Write the XML-RPC encoding of this :class:`DateTime` item to the *out* stream
334       Write the XML-RPC base 64 encoding of this binary item to the *out* stream object.
339       XML-RPC spec was written.
375    A :class:`Fault` object encapsulates the content of an XML-RPC fault tag. Fault
533    Convert any Python value to one of the XML-RPC Boolean constants, ``True`` or
539    Convert *params* into an XML-RPC request. or into a response if *methodresponse*
543    supplied, is the encoding to use in the generated XML; the default is UTF-8.
544    Python's :const:`None` value cannot be used in standard XML-RPC; to allow using
550    Convert an XML-RPC request or response into Python objects, a ``(params,
552    ``None`` if no method name is present in the packet. If the XML-RPC packet
568    # simple test program (from the XML-RPC specification)
581 To access an XML-RPC server through a HTTP proxy, you need to define a custom