$58 GRAYBYTE WORDPRESS FILE MANAGER $53

U

i�f��@sbdZd
Z
Gdd�d�ZGdd�de�ZGdd�de�ZGdd	�d	e�ZGd
d�de�Zdd
�ZdS)zAbstract Protocol base classes.)�BaseProtocol�Protocol�DatagramProtocol�SubprocessProtocol�BufferedProtocolc@s4eZ
dZd
ZdZdd�Zdd�Zdd�Zd	d
�ZdS)r
a
Common base class for protocol interfaces.

    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
    �c
Csd
S)z�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.
        Nr)�selfZ	transportrr�6/opt/alt/python38/lib64/python3.8/asyncio/protocols.py�connection_mades
zBaseProtocol.connection_madec
Csd
S)z�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).
        Nr�r�excrrr�connection_losts
zBaseProtocol.connection_lostc


Csd
S)aCalled 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).
        Nr�
rrrr�
pause_writing%s
zBaseProtocol.pause_writingc


Csd
S)zvCalled when the transport's buffer drains below the low-water mark.

        See pause_writing() for details.
        Nrr
rrr�resume_writing;s
zBaseProtocol.resume_writingN)	�__name__�
__module__�__qualname__�__doc__�	__slots__r	rrrrrrrr
	s
	r
c@s$eZ
dZd
ZdZdd�Zdd�ZdS)ranInterface for stream protocol.

    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

    * CM: connection_made()
    * DR: data_received()
    * ER: eof_received()
    * CL: connection_lost()
    rc
Csd
S)zTCalled when some data is received.

        The argument is a bytes object.
        Nr)r�datarrr�
data_received^s
zProtocol.data_receivedc


Csd
S�z�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.
        Nrr
rrr�eof_receivedds
zProtocol.eof_receivedN)rrrrrrrrrrrrBs
rc@s,eZ
dZd
ZdZdd�Zdd�Zdd�Zd	S)
ra�Interface for stream protocol with manual buffer control.

    Important: this has been added to asyncio in Python 3.7
    *on a provisional basis*!  Consider it as an experimental API that
    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()
    rc
Csd
S)aP
Called to allocate a new receive buffer.

        *sizehint* is a recommended minimal size for the returned
        buffer.  When set to -1, the buffer size can be arbitrary.

        Must return an object that implements the
        :ref:`buffer protocol <bufferobjects>`.
        It is an error to return a zero-sized buffer.
        Nr)r�sizehintrrr�
get_buffer�s
zBufferedProtocol.get_bufferc
Csd
S)z�Called when the buffer was updated with the received data.

        *nbytes* is the total number of bytes that were written to
        the buffer.
        Nr)r�nbytesrrr�buffer_updated�s
zBufferedProtocol.buffer_updatedc


Csd
Srrr
rrrr�s
zBufferedProtocol.eof_receivedN)rrrrrrrrrrrrrms

rc@s$eZ
dZd
ZdZdd�Zdd�ZdS)rz Interface for datagram protocol.rc
Csd
S)z&Called when some datagram is received.Nr)rrZaddrrrr�datagram_received�s
z"DatagramProtocol.datagram_receivedc
Csd
S)z~Called when a send or receive operation raises an OSError.

        (Other than BlockingIOError or InterruptedError.)
        Nrr
rrr�error_received�s
zDatagramProtocol.error_receivedN)rrrrrrrrrrrr�s
rc@s,eZ
dZd
ZdZdd�Zdd�Zdd�Zd	S)
rz,Interface for protocol for subprocess calls.rc
Csd
S)z�Called when the subprocess writes data into stdout/stderr pipe.

        fd is int file descriptor.
        data is bytes object.
        Nr)r�fdrrrr�pipe_data_received�s
z%SubprocessProtocol.pipe_data_receivedc
Csd
S)z�Called when a file descriptor associated with the child process is
        closed.

        fd is the int file descriptor that was closed.
        Nr)rrrrrr�pipe_connection_lost�s
z'SubprocessProtocol.pipe_connection_lostc


Csd
S)z"Called when subprocess has exited.Nrr
rrr�process_exited�s
z!SubprocessProtocol.process_exitedN)rrrrrr r!r"rrrrr�s

rcCs�t|
�
}|r�|�
|�
}t|�
}|s*td
�
�
||krL|
|d|�<|�|�

dS|
d|�|d|�<|�|�

|
|d�}
t|
�
}qdS)Nz%get_buffer() returned an empty buffer)�lenr�RuntimeErrorr)�protorZdata_lenZbufZbuf_lenrrr�_feed_data_to_buffered_proto�s














r&N)r�__all__r
rrrrr&rrrr�<module>
s9+9