python-docs-pl/library/asyncio-protocol.po at 3.9 · python/python-docs-pl

854 lines (671 loc) · 24.7 KB
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2021, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
# Translators:
# Stefan Ocetkiewicz <stefan.ocetkiewicz@gmail.com>, 2020
# Seweryn Piórkowski <seweryn.piorkowski@gmail.com>, 2020
# Maciej Olko <maciej.olko@gmail.com>, 2020
"Project-Id-Version: Python 3.9\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-05-15 06:22+0000\n"
"PO-Revision-Date: 2017-02-16 17:49+0000\n"
"Last-Translator: Maciej Olko <maciej.olko@gmail.com>, 2020\n"
"Language-Team: Polish (https://www.transifex.com/python-doc/teams/5390/pl/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: pl\n"
"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && "
"(n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && "
"n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n"
msgid "Transports and Protocols"
msgid "Preface"
"Transports and Protocols are used by the **low-level** event loop APIs such "
"as :meth:`loop.create_connection`.  They use callback-based programming "
"style and enable high-performance implementations of network or IPC "
"protocols (e.g. HTTP)."
"Essentially, transports and protocols should only be used in libraries and "
"frameworks and never in high-level asyncio applications."
msgid "This documentation page covers both `Transports`_ and `Protocols`_."
msgid "Introduction"
msgstr "Wprowadzenie"
"At the highest level, the transport is concerned with *how* bytes are "
"transmitted, while the protocol determines *which* bytes to transmit (and to "
"some extent when)."
"A different way of saying the same thing: a transport is an abstraction for "
"a socket (or similar I/O endpoint) while a protocol is an abstraction for an "
"application, from the transport's point of view."
"Yet another view is the transport and protocol interfaces together define an "
"abstract interface for using network I/O and interprocess I/O."
"There is always a 1:1 relationship between transport and protocol objects: "
"the protocol calls transport methods to send data, while the transport calls "
"protocol methods to pass it data that has been received."
"Most of connection oriented event loop methods (such as :meth:`loop."
"create_connection`) usually accept a *protocol_factory* argument used to "
"create a *Protocol* object for an accepted connection, represented by a "
"*Transport* object. Such methods usually return a tuple of ``(transport, "
"protocol)``."
msgid "Contents"
msgstr "Zawartość"
msgid "This documentation page contains the following sections:"
"The `Transports`_ section documents asyncio :class:`BaseTransport`, :class:"
"`ReadTransport`, :class:`WriteTransport`, :class:`Transport`, :class:"
"`DatagramTransport`, and :class:`SubprocessTransport` classes."
"The `Protocols`_ section documents asyncio :class:`BaseProtocol`, :class:"
"`Protocol`, :class:`BufferedProtocol`, :class:`DatagramProtocol`, and :class:"
"`SubprocessProtocol` classes."
"The `Examples`_ section showcases how to work with transports, protocols, "
"and low-level event loop APIs."
msgid "Transports"
msgid "**Source code:** :source:`Lib/asyncio/transports.py`"
"Transports are classes provided by :mod:`asyncio` in order to abstract "
"various kinds of communication channels."
"Transport objects are always instantiated by an :ref:`asyncio event loop "
"<asyncio-event-loop>`."
"asyncio implements transports for TCP, UDP, SSL, and subprocess pipes. The "
"methods available on a transport depend on the transport's kind."
"The transport classes are :ref:`not thread safe <asyncio-multithreading>`."
msgid "Transports Hierarchy"
"Base class for all transports.  Contains methods that all asyncio transports "
msgid "A base transport for write-only connections."
"Instances of the *WriteTransport* class are returned from the :meth:`loop."
"connect_write_pipe` event loop method and are also used by subprocess-"
"related methods like :meth:`loop.subprocess_exec`."
msgid "A base transport for read-only connections."
"Instances of the *ReadTransport* class are returned from the :meth:`loop."
"connect_read_pipe` event loop method and are also used by subprocess-related "
"methods like :meth:`loop.subprocess_exec`."
"Interface representing a bidirectional transport, such as a TCP connection."
"The user does not instantiate a transport directly; they call a utility "
"function, passing it a protocol factory and other information necessary to "
"create the transport and protocol."
"Instances of the *Transport* class are returned from or used by event loop "
"methods like :meth:`loop.create_connection`, :meth:`loop."
"create_unix_connection`, :meth:`loop.create_server`, :meth:`loop.sendfile`, "
msgid "A transport for datagram (UDP) connections."
"Instances of the *DatagramTransport* class are returned from the :meth:`loop."
"create_datagram_endpoint` event loop method."
"An abstraction to represent a connection between a parent and its child OS "
"Instances of the *SubprocessTransport* class are returned from event loop "
"methods :meth:`loop.subprocess_shell` and :meth:`loop.subprocess_exec`."
msgid "Base Transport"
msgid "Close the transport."
"If the transport has a buffer for outgoing data, buffered data will be "
"flushed asynchronously.  No more data will be received.  After all buffered "
"data is flushed, the protocol's :meth:`protocol.connection_lost() "
"<BaseProtocol.connection_lost>` method will be called with :const:`None` as "
"its argument."
msgid "Return ``True`` if the transport is closing or is closed."
msgid "Return information about the transport or underlying resources it uses."
"*name* is a string representing the piece of transport-specific information "
"*default* is the value to return if the information is not available, or if "
"the transport does not support querying it with the given third-party event "
"loop implementation or on the current platform."
"For example, the following code attempts to get the underlying socket object "
"of the transport::"
msgid "Categories of information that can be queried on some transports:"
msgid "socket:"
"``'peername'``: the remote address to which the socket is connected, result "
"of :meth:`socket.socket.getpeername` (``None`` on error)"
msgid "``'socket'``: :class:`socket.socket` instance"
"``'sockname'``: the socket's own address, result of :meth:`socket.socket."
"getsockname`"
msgid "SSL socket:"
"``'compression'``: the compression algorithm being used as a string, or "
"``None`` if the connection isn't compressed; result of :meth:`ssl.SSLSocket."
"compression`"
"``'cipher'``: a three-value tuple containing the name of the cipher being "
"used, the version of the SSL protocol that defines its use, and the number "
"of secret bits being used; result of :meth:`ssl.SSLSocket.cipher`"
"``'peercert'``: peer certificate; result of :meth:`ssl.SSLSocket.getpeercert`"
msgid "``'sslcontext'``: :class:`ssl.SSLContext` instance"
"``'ssl_object'``: :class:`ssl.SSLObject` or :class:`ssl.SSLSocket` instance"
msgid "pipe:"
msgid "``'pipe'``: pipe object"
msgid "subprocess:"
msgid "``'subprocess'``: :class:`subprocess.Popen` instance"
msgid "Set a new protocol."
"Switching protocol should only be done when both protocols are documented to "
"support the switch."
msgid "Return the current protocol."
msgid "Read-only Transports"
msgid "Return ``True`` if the transport is receiving new data."
"Pause the receiving end of the transport.  No data will be passed to the "
"protocol's :meth:`protocol.data_received() <Protocol.data_received>` method "
"until :meth:`resume_reading` is called."
"The method is idempotent, i.e. it can be called when the transport is "
"already paused or closed."
"Resume the receiving end.  The protocol's :meth:`protocol.data_received() "
"<Protocol.data_received>` method will be called once again if some data is "
"available for reading."
"The method is idempotent, i.e. it can be called when the transport is "
"already reading."
msgid "Write-only Transports"
"Close the transport immediately, without waiting for pending operations to "
"complete.  Buffered data will be lost.  No more data will be received. The "
"protocol's :meth:`protocol.connection_lost() <BaseProtocol.connection_lost>` "
"method will eventually be called with :const:`None` as its argument."
"Return :const:`True` if the transport supports :meth:`~WriteTransport."
"write_eof`, :const:`False` if not."
msgid "Return the current size of the output buffer used by the transport."
"Get the *high* and *low* watermarks for write flow control. Return a tuple "
"``(low, high)`` where *low* and *high* are positive number of bytes."
msgid "Use :meth:`set_write_buffer_limits` to set the limits."
msgid "Set the *high* and *low* watermarks for write flow control."
"These two values (measured in number of bytes) control when the protocol's :"
"meth:`protocol.pause_writing() <BaseProtocol.pause_writing>` and :meth:"
"`protocol.resume_writing() <BaseProtocol.resume_writing>` methods are "
"called. If specified, the low watermark must be less than or equal to the "
"high watermark.  Neither *high* nor *low* can be negative."
":meth:`~BaseProtocol.pause_writing` is called when the buffer size becomes "
"greater than or equal to the *high* value. If writing has been paused, :meth:"
"`~BaseProtocol.resume_writing` is called when the buffer size becomes less "
"than or equal to the *low* value."
"The defaults are implementation-specific.  If only the high watermark is "
"given, the low watermark defaults to an implementation-specific value less "
"than or equal to the high watermark.  Setting *high* to zero forces *low* to "
"zero as well, and causes :meth:`~BaseProtocol.pause_writing` to be called "
"whenever the buffer becomes non-empty.  Setting *low* to zero causes :meth:"
"`~BaseProtocol.resume_writing` to be called only once the buffer is empty. "
"Use of zero for either limit is generally sub-optimal as it reduces "
"opportunities for doing I/O and computation concurrently."
msgid "Use :meth:`~WriteTransport.get_write_buffer_limits` to get the limits."
msgid "Write some *data* bytes to the transport."
"This method does not block; it buffers the data and arranges for it to be "
"sent out asynchronously."
"Write a list (or any iterable) of data bytes to the transport. This is "
"functionally equivalent to calling :meth:`write` on each element yielded by "
"the iterable, but may be implemented more efficiently."
"Close the write end of the transport after flushing all buffered data. Data "
"may still be received."
"This method can raise :exc:`NotImplementedError` if the transport (e.g. SSL) "
"doesn't support half-closed connections."
msgid "Datagram Transports"
"Send the *data* bytes to the remote peer given by *addr* (a transport-"
"dependent target address).  If *addr* is :const:`None`, the data is sent to "
"the target address given on transport creation."
"Close the transport immediately, without waiting for pending operations to "
"complete.  Buffered data will be lost. No more data will be received.  The "
"protocol's :meth:`protocol.connection_lost() <BaseProtocol.connection_lost>` "
"method will eventually be called with :const:`None` as its argument."
msgid "Subprocess Transports"
msgid "Return the subprocess process id as an integer."
"Return the transport for the communication pipe corresponding to the integer "
"file descriptor *fd*:"
"``0``: readable streaming transport of the standard input (*stdin*), or :"
"const:`None` if the subprocess was not created with ``stdin=PIPE``"
"``1``: writable streaming transport of the standard output (*stdout*), or :"
"const:`None` if the subprocess was not created with ``stdout=PIPE``"
"``2``: writable streaming transport of the standard error (*stderr*), or :"
"const:`None` if the subprocess was not created with ``stderr=PIPE``"
msgid "other *fd*: :const:`None`"
"Return the subprocess return code as an integer or :const:`None` if it "
"hasn't returned, which is similar to the :attr:`subprocess.Popen.returncode` "
"attribute."
msgid "Kill the subprocess."
"On POSIX systems, the function sends SIGKILL to the subprocess. On Windows, "
"this method is an alias for :meth:`terminate`."
msgid "See also :meth:`subprocess.Popen.kill`."
"Send the *signal* number to the subprocess, as in :meth:`subprocess.Popen."
"send_signal`."
msgid "Stop the subprocess."
"On POSIX systems, this method sends SIGTERM to the subprocess. On Windows, "
"the Windows API function TerminateProcess() is called to stop the subprocess."
msgid "See also :meth:`subprocess.Popen.terminate`."
msgid "Kill the subprocess by calling the :meth:`kill` method."
"If the subprocess hasn't returned yet, and close transports of *stdin*, "
"*stdout*, and *stderr* pipes."
msgid "Protocols"
msgid "**Source code:** :source:`Lib/asyncio/protocols.py`"
"asyncio provides a set of abstract base classes that should be used to "
"implement network protocols.  Those classes are meant to be used together "
"with :ref:`transports <asyncio-transport>`."
"Subclasses of abstract base protocol classes may implement some or all "
"methods.  All these methods are callbacks: they are called by transports on "
"certain events, for example when some data is received. A base protocol "
"method should be called by the corresponding transport."
msgid "Base Protocols"
msgid "Base protocol with methods that all protocols share."
"The base class for implementing streaming protocols (TCP, Unix sockets, etc)."
"A base class for implementing streaming protocols with manual control of the "
"receive buffer."
msgid "The base class for implementing datagram (UDP) protocols."
"The base class for implementing protocols communicating with child processes "
"(unidirectional pipes)."
msgid "Base Protocol"
msgid "All asyncio protocols can implement Base Protocol callbacks."
msgid "Connection Callbacks"
"Connection callbacks are called on all protocols, exactly once per a "
"successful connection.  All other protocol callbacks can only be called "
"between those two methods."
msgid "Called when a connection is made."
"The *transport* argument is the transport representing the connection.  The "
"protocol is responsible for storing the reference to its transport."
msgid "Called when the connection is lost or closed."
"The argument is either an exception object or :const:`None`. The latter "
"means a regular EOF is received, or the connection was aborted or closed by "
"this side of the connection."
msgid "Flow Control Callbacks"
"Flow control callbacks can be called by transports to pause or resume "
"writing performed by the protocol."
"See the documentation of the :meth:`~WriteTransport.set_write_buffer_limits` "
"method for more details."
msgid "Called when the transport's buffer goes over the high watermark."
msgid "Called when the transport's buffer drains below the low watermark."
"If the buffer size equals the high watermark, :meth:`~BaseProtocol."
"pause_writing` is not called: the buffer size must go strictly over."
"Conversely, :meth:`~BaseProtocol.resume_writing` is called when the buffer "
"size is equal or lower than the low watermark.  These end conditions are "
"important to ensure that things go as expected when either mark is zero."
msgid "Streaming Protocols"
"Event methods, such as :meth:`loop.create_server`, :meth:`loop."
"create_unix_server`, :meth:`loop.create_connection`, :meth:`loop."
"create_unix_connection`, :meth:`loop.connect_accepted_socket`, :meth:`loop."
"connect_read_pipe`, and :meth:`loop.connect_write_pipe` accept factories "
"that return streaming protocols."
"Called when some data is received.  *data* is a non-empty bytes object "
"containing the incoming data."
"Whether the data is buffered, chunked or reassembled depends on the "
"transport.  In general, you shouldn't rely on specific semantics and instead "
"make your parsing generic and flexible. However, data is always received in "
"the correct order."
"The method can be called an arbitrary number of times while a connection is "
"However, :meth:`protocol.eof_received() <Protocol.eof_received>` is called "
"at most once.  Once `eof_received()` is called, ``data_received()`` is not "
"called anymore."
"Called when the other end signals it won't send any more data (for example "
"by calling :meth:`transport.write_eof() <WriteTransport.write_eof>`, if the "
"other end also uses asyncio)."
"This method may return a false value (including ``None``), in which case the "
"transport will close itself.  Conversely, if this method returns a true "
"value, the protocol used determines whether to close the transport. Since "
"the default implementation returns ``None``, it implicitly closes the "
"connection."
"Some transports, including SSL, don't support half-closed connections, in "
"which case returning true from this method will result in the connection "
"being closed."
msgid "State machine:"
msgid "Buffered Streaming Protocols"
"Buffered Protocols can be used with any event loop method that supports "
"`Streaming Protocols`_."
"``BufferedProtocol`` implementations allow explicit manual allocation and "
"control of 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 protocol implementations can significantly reduce the "
"number of buffer allocations."
"The following callbacks are called on :class:`BufferedProtocol` instances:"
msgid "Called to allocate a new receive buffer."
"*sizehint* is the recommended minimum size for the returned buffer.  It is "
"acceptable to return smaller or larger buffers than what *sizehint* "
"suggests.  When set to -1, the buffer size can be arbitrary. It is an error "
"to return a buffer with a zero size."
"``get_buffer()`` must return an object implementing the :ref:`buffer "
"protocol <bufferobjects>`."
msgid "Called when the buffer was updated with the received data."
msgid "*nbytes* is the total number of bytes that were written to the buffer."
"See the documentation of the :meth:`protocol.eof_received() <Protocol."
"eof_received>` method."
":meth:`~BufferedProtocol.get_buffer` can be called an arbitrary number of "
"times during a connection.  However, :meth:`protocol.eof_received() "
"<Protocol.eof_received>` is called at most once and, if called, :meth:"
"`~BufferedProtocol.get_buffer` and :meth:`~BufferedProtocol.buffer_updated` "
"won't be called after it."
msgid "Datagram Protocols"
"Datagram Protocol instances should be constructed by protocol factories "
"passed to the :meth:`loop.create_datagram_endpoint` method."
"Called when a datagram is received.  *data* is a bytes object containing the "
"incoming data.  *addr* is the address of the peer sending the data; the "
"exact format depends on the transport."
"Called when a previous send or receive operation raises an :class:"
"`OSError`.  *exc* is the :class:`OSError` instance."
"This method is called in rare conditions, when the transport (e.g. UDP) "
"detects that a datagram could not be delivered to its recipient. In many "
"conditions though, undeliverable datagrams will be silently dropped."
"On BSD systems (macOS, FreeBSD, etc.) flow control is not supported for "
"datagram protocols, because there is no reliable way to detect send failures "
"caused by writing too many packets."
"The socket always appears 'ready' and excess packets are dropped. An :class:"
"`OSError` with ``errno`` set to :const:`errno.ENOBUFS` may or may not be "
"raised; if it is raised, it will be reported to :meth:`DatagramProtocol."
"error_received` but otherwise ignored."
msgid "Subprocess Protocols"
"Subprocess Protocol instances should be constructed by protocol factories "
"passed to the :meth:`loop.subprocess_exec` and :meth:`loop.subprocess_shell` "
"Called when the child process writes data into its stdout or stderr pipe."
msgid "*fd* is the integer file descriptor of the pipe."
msgid "*data* is a non-empty bytes object containing the received data."
"Called when one of the pipes communicating with the child process is closed."
msgid "*fd* is the integer file descriptor that was closed."
msgid "Called when the child process has exited."
msgid "Examples"
msgstr "Przykłady"
msgid "TCP Echo Server"
"Create a TCP echo server using the :meth:`loop.create_server` method, send "
"back received data, and close the connection::"
"The :ref:`TCP echo server using streams <asyncio-tcp-echo-server-streams>` "
"example uses the high-level :func:`asyncio.start_server` function."
msgid "TCP Echo Client"
"A TCP echo client using the :meth:`loop.create_connection` method, sends "
"data, and waits until the connection is closed::"
"The :ref:`TCP echo client using streams <asyncio-tcp-echo-client-streams>` "
"example uses the high-level :func:`asyncio.open_connection` function."
msgid "UDP Echo Server"
"A UDP echo server, using the :meth:`loop.create_datagram_endpoint` method, "
"sends back received data::"
msgid "UDP Echo Client"
"A UDP echo client, using the :meth:`loop.create_datagram_endpoint` method, "
"sends data and closes the transport when it receives the answer::"
msgid "Connecting Existing Sockets"
"Wait until a socket receives data using the :meth:`loop.create_connection` "
"method with a protocol::"
"The :ref:`watch a file descriptor for read events "
"<asyncio_example_watch_fd>` example uses the low-level :meth:`loop."
"add_reader` method to register an FD."
"The :ref:`register an open socket to wait for data using streams "
"<asyncio_example_create_connection-streams>` example uses high-level streams "
"created by the :func:`open_connection` function in a coroutine."
msgid "loop.subprocess_exec() and SubprocessProtocol"
"An example of a subprocess protocol used to get the output of a subprocess "
"and to wait for the subprocess exit."
msgid "The subprocess is created by the :meth:`loop.subprocess_exec` method::"
"See also the :ref:`same example <asyncio_example_create_subprocess_exec>` "
"written using high-level APIs."
Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

FilesExpand file tree

asyncio-protocol.po

Latest commit

History

asyncio-protocol.po

File metadata and controls
