module documentation
Interface documentation.
Maintainer: Itamar Shtull-Trauring
Interface |
|
A list of acceptable ciphers for a TLS context. |
Interface |
|
An address, e.g. a TCP (host, port). |
Interface |
|
A TLS cipher. |
Interface |
|
Object used to interface between connections and protocols. |
Interface |
|
A consumer consumes data from a producer. |
Interface |
|
A scheduled call. |
Interface |
|
An interface representing a UNIX-style numeric file descriptor. |
Interface |
|
Protocols may implement IFileDescriptorReceiver to receive file descriptors sent to them. This is useful in conjunction with IUNIXTransport , which allows file descriptors to be sent between processes on a single host. |
Interface |
|
A descriptor that can be half-closed. |
Interface |
|
Implemented to indicate they want notification of half-closes. |
Interface |
|
An interface implemented by a IProtocol to indicate that it would like to be notified when TLS handshakes complete when run over a TLS-based transport. |
Interface |
|
An IHostnameResolver can resolve a host name and port number into a series of IAddress objects. |
Interface |
|
An IHostResolution represents represents an in-progress recursive query for a DNS name. |
Interface |
|
A listening port. |
Interface |
|
Give context information that will be used to log events generated by this item. |
Interface |
|
Additional functionality for multicast UDP. |
Interface |
|
A TLS based transport that supports using ALPN/NPN to negotiate the protocol to be used inside the encrypted tunnel. |
Interface |
|
A provider of IOpenSSLClientConnectionCreator can create OpenSSL.SSL.Connection objects for TLS clients. |
Interface |
|
A provider of IOpenSSLContextFactory is capable of generating OpenSSL.SSL.Context classes suitable for configuring TLS on a connection. A provider will store enough state to be able to generate these contexts as needed for individual connections. |
Interface |
|
A provider of IOpenSSLServerConnectionCreator can create OpenSSL.SSL.Connection objects for TLS servers. |
Interface |
|
Interface for process-related event handlers. |
Interface |
|
A process transport. |
Interface |
|
A producer produces data for a consumer. |
Interface |
|
No interface docstring; 4/4 methods documented |
Interface |
|
Interface for protocol factories. |
Interface |
|
A provider of IProtocolNegotiationFactory can provide information about the various protocols that the factory can create implementations of. This can be used, for example, to provide protocol names for Next Protocol Negotiation and Application Layer Protocol Negotiation. |
Interface |
|
A pull producer, also known as a non-streaming producer, is expected to produce data each time resumeProducing() is called. |
Interface |
|
A push producer, also known as a streaming producer is expected to produce (write to this consumer) data on a continuous basis, unless it has been paused. A paused push producer will resume producing after its ... |
Interface |
|
Core methods that a Reactor must implement. |
Interface |
|
A reactor which provides hooks that need to be called before and after daemonization. |
Interface |
|
Implement me to be able to use IFileDescriptor type resources. |
Interface |
|
This interface is the set of thread-safe methods which may be invoked on the reactor from other threads. |
Interface |
|
This interface contains the methods exposed by a reactor which will let you run functions in another thread. |
Interface |
|
UDP socket methods that support multicast. |
Interface |
|
An IReactorPluggableNameResolver is a reactor whose name resolver can be set to a user-supplied object. |
Interface |
|
An IReactorPluggableResolver is a reactor which can be customized with an IResolverSimple . This is a fairly limited interface, that supports only IPv4; you should use IReactorPluggableNameResolver instead. |
Interface |
|
No interface docstring; 1/1 method documented |
Interface |
|
Methods which allow a reactor to use externally created sockets. |
Interface |
|
No interface docstring; 2/2 methods documented |
Interface |
|
No interface docstring; 2/2 methods documented |
Interface |
|
Dispatch methods to be run in threads. |
Interface |
|
Time methods that a Reactor should implement. |
Interface |
|
UDP socket methods. |
Interface |
|
UNIX socket methods. |
Interface |
|
Datagram UNIX socket methods. |
Interface |
|
Win32 Event API methods |
Interface |
|
An IFileDescriptor that can read. |
Interface |
|
An IFileDescriptor that can both read and write. |
Interface |
|
An IResolutionReceiver receives the results of a hostname resolution in progress, initiated by an IHostnameResolver . |
Interface |
|
No interface docstring; 24/24 methods documented |
Interface |
|
No interface docstring; 1/1 method documented |
Interface |
|
An object which provides access to a collection of services. |
Interface |
|
A SSL/TLS based transport. |
Interface |
|
A stream client endpoint is a place that ClientFactory can connect to. For example, a remote TCP host/port pair would be a TCP client endpoint. |
Interface |
|
An IStreamClientEndpointStringParserWithReactor is a parser which can convert a set of string *args and **kwargs into an IStreamClientEndpoint provider. |
Interface |
|
A stream server endpoint is a place that a Factory can listen for incoming connections. |
Interface |
|
An IStreamServerEndpointStringParser is like an IStreamClientEndpointStringParserWithReactor , except for IStreamServerEndpoint s instead of clients. It integrates with endpoints.serverFromString in much the same way. |
Interface |
|
An object that wraps a networking OS-specific handle. |
Interface |
|
A TCP based transport. |
Interface |
|
A TCP transport that supports switching to TLS midstream. |
Interface |
|
I am a transport for bytes. |
Interface |
|
Transport for UDP DatagramProtocols. |
Interface |
|
Transport for UDP ConnectedPacketProtocols. |
Interface |
|
Transport for UDP PacketProtocols. |
Interface |
|
Transport for stream-oriented unix domain connections. |
Interface |
|
An IFileDescriptor that can write. |
Interface | _ |
An implementor of _ISupportsExitSignalCapturing will capture the value of any delivered exit signal (SIGINT, SIGTERM, SIGBREAK) for which it has installed a handler. The caught signal number is made available in the _exitSignal attribute. |