2017-12-10 19:36:12 -04:00
|
|
|
"""Abstract Protocol base classes."""
|
2013-10-17 17:40:50 -03:00
|
|
|
|
2017-12-10 19:36:12 -04:00
|
|
|
__all__ = (
|
|
|
|
'BaseProtocol', 'Protocol', 'DatagramProtocol',
|
2018-01-28 17:30:26 -04:00
|
|
|
'SubprocessProtocol', 'BufferedProtocol',
|
2017-12-10 19:36:12 -04:00
|
|
|
)
|
2013-10-17 17:40:50 -03:00
|
|
|
|
|
|
|
|
|
|
|
class BaseProtocol:
|
2013-11-30 19:35:42 -04:00
|
|
|
"""Common base class for protocol interfaces.
|
2013-10-17 17:40:50 -03:00
|
|
|
|
|
|
|
Usually user implements protocols that derived from BaseProtocol
|
|
|
|
like Protocol or ProcessProtocol.
|
|
|
|
|
|
|
|
The only case when BaseProtocol should be implemented directly is
|
|
|
|
write-only transport like write pipe
|
|
|
|
"""
|
|
|
|
|
|
|
|
def connection_made(self, transport):
|
|
|
|
"""Called when a connection is made.
|
|
|
|
|
|
|
|
The argument is the transport representing the pipe connection.
|
|
|
|
To receive data, wait for data_received() calls.
|
|
|
|
When the connection is closed, connection_lost() is called.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def connection_lost(self, exc):
|
|
|
|
"""Called when the connection is lost or closed.
|
|
|
|
|
|
|
|
The argument is an exception object or None (the latter
|
|
|
|
meaning a regular EOF is received or the connection was
|
|
|
|
aborted or closed).
|
|
|
|
"""
|
|
|
|
|
2013-10-18 19:17:11 -03:00
|
|
|
def pause_writing(self):
|
|
|
|
"""Called when the transport's buffer goes over the high-water mark.
|
|
|
|
|
|
|
|
Pause and resume calls are paired -- pause_writing() is called
|
|
|
|
once when the buffer goes strictly over the high-water mark
|
|
|
|
(even if subsequent writes increases the buffer size even
|
|
|
|
more), and eventually resume_writing() is called once when the
|
|
|
|
buffer size reaches the low-water mark.
|
|
|
|
|
|
|
|
Note that if the buffer size equals the high-water mark,
|
|
|
|
pause_writing() is not called -- it must go strictly over.
|
|
|
|
Conversely, resume_writing() is called when the buffer size is
|
|
|
|
equal or lower than the low-water mark. These end conditions
|
|
|
|
are important to ensure that things go as expected when either
|
|
|
|
mark is zero.
|
|
|
|
|
|
|
|
NOTE: This is the only Protocol callback that is not called
|
|
|
|
through EventLoop.call_soon() -- if it were, it would have no
|
|
|
|
effect when it's most needed (when the app keeps writing
|
|
|
|
without yielding until pause_writing() is called).
|
|
|
|
"""
|
|
|
|
|
|
|
|
def resume_writing(self):
|
|
|
|
"""Called when the transport's buffer drains below the low-water mark.
|
|
|
|
|
|
|
|
See pause_writing() for details.
|
|
|
|
"""
|
|
|
|
|
2013-10-17 17:40:50 -03:00
|
|
|
|
|
|
|
class Protocol(BaseProtocol):
|
2013-11-30 19:35:42 -04:00
|
|
|
"""Interface for stream protocol.
|
2013-10-17 17:40:50 -03:00
|
|
|
|
|
|
|
The user should implement this interface. They can inherit from
|
|
|
|
this class but don't need to. The implementations here do
|
|
|
|
nothing (they don't raise exceptions).
|
|
|
|
|
|
|
|
When the user wants to requests a transport, they pass a protocol
|
|
|
|
factory to a utility function (e.g., EventLoop.create_connection()).
|
|
|
|
|
|
|
|
When the connection is made successfully, connection_made() is
|
|
|
|
called with a suitable transport object. Then data_received()
|
|
|
|
will be called 0 or more times with data (bytes) received from the
|
|
|
|
transport; finally, connection_lost() will be called exactly once
|
|
|
|
with either an exception object or None as an argument.
|
|
|
|
|
|
|
|
State machine of calls:
|
|
|
|
|
|
|
|
start -> CM [-> DR*] [-> ER?] -> CL -> end
|
2015-01-29 08:33:15 -04:00
|
|
|
|
|
|
|
* CM: connection_made()
|
|
|
|
* DR: data_received()
|
|
|
|
* ER: eof_received()
|
|
|
|
* CL: connection_lost()
|
2013-10-17 17:40:50 -03:00
|
|
|
"""
|
|
|
|
|
|
|
|
def data_received(self, data):
|
|
|
|
"""Called when some data is received.
|
|
|
|
|
|
|
|
The argument is a bytes object.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def eof_received(self):
|
|
|
|
"""Called when the other end calls write_eof() or equivalent.
|
|
|
|
|
|
|
|
If this returns a false value (including None), the transport
|
|
|
|
will close itself. If it returns a true value, closing the
|
|
|
|
transport is up to the protocol.
|
|
|
|
"""
|
|
|
|
|
|
|
|
|
2018-01-28 17:30:26 -04:00
|
|
|
class BufferedProtocol(BaseProtocol):
|
|
|
|
"""Interface for stream protocol with manual buffer control.
|
|
|
|
|
2018-03-28 17:05:24 -03:00
|
|
|
Important: this has been added to asyncio in Python 3.7
|
2018-01-29 00:51:08 -04:00
|
|
|
*on a provisional basis*! Consider it as an experimental API that
|
2018-01-28 17:30:26 -04:00
|
|
|
might be changed or removed in Python 3.8.
|
|
|
|
|
|
|
|
Event methods, such as `create_server` and `create_connection`,
|
|
|
|
accept factories that return protocols that implement this interface.
|
|
|
|
|
|
|
|
The idea of BufferedProtocol is that it allows to manually allocate
|
|
|
|
and control the receive buffer. Event loops can then use the buffer
|
|
|
|
provided by the protocol to avoid unnecessary data copies. This
|
|
|
|
can result in noticeable performance improvement for protocols that
|
|
|
|
receive big amounts of data. Sophisticated protocols can allocate
|
|
|
|
the buffer only once at creation time.
|
|
|
|
|
|
|
|
State machine of calls:
|
|
|
|
|
|
|
|
start -> CM [-> GB [-> BU?]]* [-> ER?] -> CL -> end
|
|
|
|
|
|
|
|
* CM: connection_made()
|
|
|
|
* GB: get_buffer()
|
|
|
|
* BU: buffer_updated()
|
|
|
|
* ER: eof_received()
|
|
|
|
* CL: connection_lost()
|
|
|
|
"""
|
|
|
|
|
|
|
|
def get_buffer(self):
|
|
|
|
"""Called to allocate a new receive buffer.
|
|
|
|
|
|
|
|
Must return an object that implements the
|
|
|
|
:ref:`buffer protocol <bufferobjects>`.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def buffer_updated(self, nbytes):
|
|
|
|
"""Called when the buffer was updated with the received data.
|
|
|
|
|
|
|
|
*nbytes* is the total number of bytes that were written to
|
|
|
|
the buffer.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def eof_received(self):
|
|
|
|
"""Called when the other end calls write_eof() or equivalent.
|
|
|
|
|
|
|
|
If this returns a false value (including None), the transport
|
|
|
|
will close itself. If it returns a true value, closing the
|
|
|
|
transport is up to the protocol.
|
|
|
|
"""
|
|
|
|
|
|
|
|
|
2013-10-17 17:40:50 -03:00
|
|
|
class DatagramProtocol(BaseProtocol):
|
2013-11-30 19:35:42 -04:00
|
|
|
"""Interface for datagram protocol."""
|
2013-10-17 17:40:50 -03:00
|
|
|
|
|
|
|
def datagram_received(self, data, addr):
|
|
|
|
"""Called when some datagram is received."""
|
|
|
|
|
2013-11-15 20:51:48 -04:00
|
|
|
def error_received(self, exc):
|
|
|
|
"""Called when a send or receive operation raises an OSError.
|
|
|
|
|
|
|
|
(Other than BlockingIOError or InterruptedError.)
|
|
|
|
"""
|
2013-10-17 17:40:50 -03:00
|
|
|
|
|
|
|
|
|
|
|
class SubprocessProtocol(BaseProtocol):
|
2013-11-30 19:35:42 -04:00
|
|
|
"""Interface for protocol for subprocess calls."""
|
2013-10-17 17:40:50 -03:00
|
|
|
|
|
|
|
def pipe_data_received(self, fd, data):
|
2013-11-15 20:51:48 -04:00
|
|
|
"""Called when the subprocess writes data into stdout/stderr pipe.
|
2013-10-17 17:40:50 -03:00
|
|
|
|
2014-02-18 23:27:48 -04:00
|
|
|
fd is int file descriptor.
|
2013-10-17 17:40:50 -03:00
|
|
|
data is bytes object.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def pipe_connection_lost(self, fd, exc):
|
|
|
|
"""Called when a file descriptor associated with the child process is
|
|
|
|
closed.
|
|
|
|
|
|
|
|
fd is the int file descriptor that was closed.
|
|
|
|
"""
|
|
|
|
|
|
|
|
def process_exited(self):
|
2013-11-15 20:51:48 -04:00
|
|
|
"""Called when subprocess has exited."""
|
2018-01-28 17:30:26 -04:00
|
|
|
|
|
|
|
|
|
|
|
def _is_buffered_protocol(proto):
|
|
|
|
return hasattr(proto, 'get_buffer') and not hasattr(proto, 'data_received')
|