python-docs-tr/library/asynchat.po at 3.11 · python/python-docs-tr

243 lines (208 loc) · 8.12 KB
# Python Documentation Turkish Translation
# Copyright (C) 2001-2023, Python Software Foundation
# This file is distributed under the same license as the Python package.
"Project-Id-Version: Python 3.11\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-03-01 00:18+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: \n"
"Language-Team: TURKISH <python.docs.tr@gmail.com>\n"
"Language: tr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: library/asynchat.rst:2
msgid ":mod:`asynchat` --- Asynchronous socket command/response handler"
#: library/asynchat.rst:11
msgid "**Source code:** :source:`Lib/asynchat.py`"
#: library/asynchat.rst:17
"The :mod:`asynchat` module is deprecated (see :pep:`PEP 594 <594#asynchat>` "
"for details). Please use :mod:`asyncio` instead."
#: library/asynchat.rst:22
"This module exists for backwards compatibility only.  For new code we "
"recommend using :mod:`asyncio`."
#: library/asynchat.rst:25
"This module builds on the :mod:`asyncore` infrastructure, simplifying "
"asynchronous clients and servers and making it easier to handle protocols "
"whose elements are terminated by arbitrary strings, or are of variable "
"length. :mod:`asynchat` defines the abstract class :class:`async_chat` that "
"you subclass, providing implementations of the :meth:`collect_incoming_data` "
"and :meth:`found_terminator` methods. It uses the same asynchronous loop as :"
"mod:`asyncore`, and the two types of channel, :class:`asyncore.dispatcher` "
"and :class:`asynchat.async_chat`, can freely be mixed in the channel map. "
"Typically an :class:`asyncore.dispatcher` server channel generates new :"
"class:`asynchat.async_chat` channel objects as it receives incoming "
"connection requests."
#: includes/wasm-notavail.rst:3
msgid ":ref:`Availability <availability>`: not Emscripten, not WASI."
#: includes/wasm-notavail.rst:5
"This module does not work or is not available on WebAssembly platforms "
"``wasm32-emscripten`` and ``wasm32-wasi``. See :ref:`wasm-availability` for "
"more information."
#: library/asynchat.rst:41
"This class is an abstract subclass of :class:`asyncore.dispatcher`. To make "
"practical use of the code you must subclass :class:`async_chat`, providing "
"meaningful :meth:`collect_incoming_data` and :meth:`found_terminator` "
"methods. The :class:`asyncore.dispatcher` methods can be used, although not "
"all make sense in a message/response context."
#: library/asynchat.rst:48
"Like :class:`asyncore.dispatcher`, :class:`async_chat` defines a set of "
"events that are generated by an analysis of socket conditions after a :c:"
"func:`select` call. Once the polling loop has been started the :class:"
"`async_chat` object's methods are called by the event-processing framework "
"with no action on the part of the programmer."
#: library/asynchat.rst:54
"Two class attributes can be modified, to improve performance, or possibly "
"even to conserve memory."
#: library/asynchat.rst:60
msgid "The asynchronous input buffer size (default ``4096``)."
#: library/asynchat.rst:65
msgid "The asynchronous output buffer size (default ``4096``)."
#: library/asynchat.rst:67
"Unlike :class:`asyncore.dispatcher`, :class:`async_chat` allows you to "
"define a :abbr:`FIFO (first-in, first-out)` queue of *producers*. A producer "
"need have only one method, :meth:`more`, which should return data to be "
"transmitted on the channel. The producer indicates exhaustion (*i.e.* that "
"it contains no more data) by having its :meth:`more` method return the empty "
"bytes object. At this point the :class:`async_chat` object removes the "
"producer from the queue and starts using the next producer, if any. When the "
"producer queue is empty the :meth:`handle_write` method does nothing. You "
"use the channel object's :meth:`set_terminator` method to describe how to "
"recognize the end of, or an important breakpoint in, an incoming "
"transmission from the remote endpoint."
#: library/asynchat.rst:80
"To build a functioning :class:`async_chat` subclass your  input methods :"
"meth:`collect_incoming_data` and :meth:`found_terminator` must handle the "
"data that the channel receives asynchronously. The methods are described "
#: library/asynchat.rst:88
"Pushes a ``None`` on to the producer queue. When this producer is popped off "
"the queue it causes the channel to be closed."
#: library/asynchat.rst:94
"Called with *data* holding an arbitrary amount of received data.  The "
"default method, which must be overridden, raises a :exc:"
"`NotImplementedError` exception."
#: library/asynchat.rst:101
"In emergencies this method will discard any data held in the input and/or "
"output buffers and the producer queue."
#: library/asynchat.rst:107
"Called when the incoming data stream  matches the termination condition set "
"by :meth:`set_terminator`. The default method, which must be overridden, "
"raises a :exc:`NotImplementedError` exception. The buffered input data "
"should be available via an instance attribute."
#: library/asynchat.rst:115
msgid "Returns the current terminator for the channel."
#: library/asynchat.rst:120
"Pushes data on to the channel's queue to ensure its transmission. This is "
"all you need to do to have the channel write the data out to the network, "
"although it is possible to use your own producers in more complex schemes to "
"implement encryption and chunking, for example."
#: library/asynchat.rst:128
"Takes a producer object and adds it to the producer queue associated with "
"the channel.  When all currently pushed producers have been exhausted the "
"channel will consume this producer's data by calling its :meth:`more` method "
"and send the data to the remote endpoint."
#: library/asynchat.rst:136
"Sets the terminating condition to be recognized on the channel.  ``term`` "
"may be any of three types of value, corresponding to three different ways to "
"handle incoming protocol data."
#: library/asynchat.rst:141
msgid "term"
#: library/asynchat.rst:141
msgid "Description"
#: library/asynchat.rst:143
msgid "*string*"
#: library/asynchat.rst:143
"Will call :meth:`found_terminator` when the string is found in the input "
#: library/asynchat.rst:146
msgid "*integer*"
#: library/asynchat.rst:146
"Will call :meth:`found_terminator` when the indicated number of characters "
"have been received"
#: library/asynchat.rst:150
msgid "``None``"
#: library/asynchat.rst:150
msgid "The channel continues to collect data forever"
#: library/asynchat.rst:154
"Note that any data following the terminator will be available for reading by "
"the channel after :meth:`found_terminator` is called."
#: library/asynchat.rst:161
msgid "asynchat Example"
#: library/asynchat.rst:163
"The following partial example shows how HTTP requests can be read with :"
"class:`async_chat`.  A web server might create an :class:"
"`http_request_handler` object for each incoming client connection. Notice "
"that initially the channel terminator is set to match the blank line at the "
"end of the HTTP headers, and a flag indicates that the headers are being "
#: library/asynchat.rst:170
"Once the headers have been read, if the request is of type POST (indicating "
"that further data are present in the input stream) then the ``Content-Length:"
"`` header is used to set a numeric terminator to read the right amount of "
"data from the channel."
#: library/asynchat.rst:175
"The :meth:`handle_request` method is called once all relevant input has been "
"marshalled, after setting the channel terminator to ``None`` to ensure that "
"any extraneous data sent by the web client are ignored. ::"
Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

FilesExpand file tree

asynchat.po

Latest commit

History

asynchat.po

File metadata and controls
