Files changed (31)
+* Alexey Borzenkov, for finding and fixing issues with Windows error detection (#66, #69), reducing dependencies in zeromq hub (#71)
+* wsgi.py now distinguishes between an empty query string ("") and a non-existent query string (no entry in environ).
+* Better behavior in tpool when you give it nonsensical numbers, thanks to R. Tyler for the nonsense. :)
This is a libevent-based backend and is thus the fastest. It's disabled by default, because it does not support native threads, but you can enable it yourself if your use case doesn't require them. (You have to install pyevent, too.)
+ `ZeroMQ <http://zeromq.org>`_-powered hub. This hub supports all normal non-blocking socket operations, and it's required for :mod:`eventlet.green.zeromq` to work.
If the selected hub is not idea for the application, another can be selected. You can make the selection either with the environment variable :ref:`EVENTLET_HUB <env_vars>`, or with use_hub.
+:mod:`pyzmq <zmq>` _ Is a python binding to the C++ ØMQ _ library written in Cython _. The following is
<p>Alternately, you can download the source tarball from <a href="http://pypi.python.org/pypi/eventlet/">PyPi</a>:
+"A ØMQ socket is what you get when you take a normal TCP socket, inject it with a mix of radioactive isotopes stolen
+from a secret Soviet atomic research project, bombard it with 1950-era cosmic rays, and put it into the hands of a drug-addled
+Generally speaking, conventional sockets present a synchronous interface to either connection-oriented reliable byte streams (SOCK_STREAM),
+or connection-less unreliable datagrams (SOCK_DGRAM). In comparison, 0MQ sockets present an abstraction of an asynchronous message queue,
+with the exact queueing semantics depending on the socket type in use. Where conventional sockets transfer streams of bytes or discrete datagrams,
+0MQ sockets being asynchronous means that the timings of the physical connection setup and teardown,
+Conventional sockets allow only strict one-to-one (two peers), many-to-one (many clients, one server),
+while simultaneously accepting incoming connections from multiple endpoints bound to the socket using bind(), thus allowing many-to-many relationships.
+"""The :mod:`zmq` module wraps the :class:`Socket` and :class:`Context` found in :mod:`pyzmq <zmq>` to be non blocking
:param custom_pool: A custom GreenPool instance which is used to spawn client green threads. If this is supplied, max_size is ignored.
:param keepalive: If set to False, disables keepalives on the server; all connections will be closed after serving one request.
:param log_format: A python format string that is used as the template to generate log lines. The following values can be formatted into it: client_ip, date_time, request_line, status_code, body_length, wall_seconds. The default is a good example of how to use it.
+ :param debug: True if the server should send exception tracebacks to the clients on 500 errors. If False, the server will respond with empty bodies.