This class is the abstract base class for all server transport implementations. Unlike the client transports, this class does not define a pure-virtual method that needs to be implemented by all base classes.
If there is a call to start the main loop, it’s conventionally called serve_forever().
Calls create_in_document and decompose_incoming_envelope to get method_request string in order to generate contexts.
Uses the ctx.in_string to set ctx.in_body_doc, which in turn is used to set ctx.in_object.
Calls the matched method using the ctx.in_object to get ctx.out_object.
Uses the ctx.out_object to set ctx.out_document and later ctx.out_object.
The transport type, conventionally defined by the URI string to its definition.
A server transport uses http as transport, and wsgi as bridge api.
A PEP-3333 compliant callable class.
Called right before the wsdl data is returned to the client.
Called right after an exception is thrown during wsdl generation. The exception object is stored in ctx.transport.wsdl_error attribute.
Called first when the incoming http request is identified as a rpc request.
Called right before the output stream is returned to the WSGI handler.
Called right before returning the exception to the client.
Called after the whole data has been returned to the client. It’s called both from success and error cases.
This function is only called by the HttpRpc protocol to have the wsgi environment parsed into ctx.in_body_doc and ctx.in_header_doc.
Calls create_in_document and decompose_incoming_envelope to get method_request string in order to generate contexts.
Uses the ctx.in_string to set ctx.in_body_doc, which in turn is used to set ctx.in_object.
Calls the matched method using the ctx.in_object to get ctx.out_object.
Uses the ctx.out_object to set ctx.out_document and later ctx.out_object.
Implement your event loop here.
The WSGI-Specific method context. WSGI-Specific information is stored in the transport attribute using the WsgiTransportContext class.
The public name of the method the method_request_string was matched to.
Holds the WSGI-specific information
The class that is used in the transport attribute of the WsgiMethodContext class.
WSGI Request environment
HTTP Request verb, as a convenience to users.
The spyne.server.zeromq module contains a server implementation that uses ZeroMQ (zmq.REP) as transport.
The ZeroMQ server transport.
Calls create_in_document and decompose_incoming_envelope to get method_request string in order to generate contexts.
Uses the ctx.in_string to set ctx.in_body_doc, which in turn is used to set ctx.in_object.
Calls the matched method using the ctx.in_object to get ctx.out_object.
Uses the ctx.out_object to set ctx.out_document and later ctx.out_object.
The public name of the method the method_request_string was matched to.
The ZeroMQ context.
The spyne.server.null module contains the NullServer class and its helper objects.
The name comes from the “null modem connection”. Look it up.
A server that doesn’t support any transport at all – it’s implemented to test services without having to run a server.
It implicitly uses the ‘sync’ auxiliary processing mode.
**kwargs overwrite *args.
You can do:
logging.getLogger('spyne.server.null').setLevel(logging.CRITICAL)
to hide context delimiters in logs.
Calls create_in_document and decompose_incoming_envelope to get method_request string in order to generate contexts.
Uses the ctx.in_string to set ctx.in_body_doc, which in turn is used to set ctx.in_object.
Calls the matched method using the ctx.in_object to get ctx.out_object.
Uses the ctx.out_object to set ctx.out_document and later ctx.out_object.
Implement your event loop here.