# Gevent-socketio documentation ## I ntroduction Socket.IO is a WebSocket-like abstraction that enables real-time communication between a browser and a server. gevent-socketio is a Python implementation single gevent-based API that works across the different WSGI-based web frameworks out there (Pyramid, Pylons, Flask, web2py, Django, etc...). Only ~3 lines of code are required to tie-in gevent-socketio gevent-socketio in your framework. Note: you need to use the gevent python WSGI server to use gevent-socketio. Namespaces: since you mostly have one websocket/socket.io endpoint per website, it is important to be

# gevent-socketio Documentation Release 0.3.1 Jeffrey Gelens, Alex Bourget, John Anderson March 19, 2015 Powered by TCPDF (www.tcpdf.org) 1 Introduction 1 2 Concepts 3 3 Getting started 5 4 Examples a WebSocket-like abstraction that enables real-time communication between a browser and a server. gevent-socketio is a Python implementation of the protocol. The reference server implementation of Socket single gevent-based API that works across the different WSGI-based web frameworks out there (Pyramid, Pylons, Flask, web2py, Django, etc...). Only ~3 lines of code are required to tie-in gevent-socketio

concurrently on one or more worker nodes using multiprocessing, Eventlet [http://eventlet.net/] or gevent [http://gevent.org/]. Tasks can execute asynchronously (in the background) or synchronously (wait until ready) temporarily congested).| |Concurrency|Concurrency is achieved by using multiprocessing, Eventlet, gevent or a mix of these.| |Scheduling|Supports recurring tasks like cron, or specifying an exact date or You can use a custom pool class name, or select one of the built-in aliases: processes, eventlet, gevent. Default is processes. ## CELERYD_AUTOSCALER Name of the autoscaler class to use. Default is

concurrently on one or more worker nodes using multiprocessing, Eventlet [http://eventlet.net/] or gevent [http://gevent.org/]. Tasks can execute asynchronously (in the background) or synchronously (wait until ready) temporarily congested).| |Concurrency|Concurrency is achieved by using multiprocessing, Eventlet, gevent or a mix of these.| |Scheduling|Supports recurring tasks like cron, or specifying an exact date or connections. This number can be tweaked depending on the number of threads/greenthreads (eventlet/gevent) using a connection. For example, running eventlet with 1000 greenlets that use a connection to the

RabbitMQ, Redis, Amazon SQS, and more... • Concurrency • prefork • (multiprocessing), • Eventlet, gevent • solo (single threaded) ## • Result Stores • AMQP, Redis • Memcached, • SQLAlchemy, Django yaml serializer. Concurrency celery[eventlet]: for using the eventlet pool. celery[gevent]: for using the gevent pool. Transports and Backends celery[librabbitmq]: for using the librabbitmq C library degrade performance instead. Including the default prefork pool, Celery also supports using Eventlet, Gevent, and running in a single thread (see Concurrency). – Events is an option that when enabled causes

Amazon SQS, (exp) • and more... ## • Concurrency • prefork (multiprocessing), • Eventlet, gevent • threads/single threaded ## • Result Stores o AMQP, Redis o memcached, MongoDB ○ SQLAlchemy yaml serializer. Concurrency celery[eventlet]: for using the eventlet pool. celery[gevent]: for using the gevent pool. celery[threads]: for using the thread pool. ## Transports and Backends ## celery[librabbitmq]: degrade performance instead. Including the default prefork pool, Celery also supports using Eventlet, Gevent, and threads (see Concurrency). – Events is an option that when enabled causes Celery to send monitoring

(exp), Amazon SQS, (exp) • and more... • Concurrency • prefork (multiprocessing), • Eventlet, gevent • threads/single threaded • Result Stores • AMQP, Redis • memcached, MongoDB • SQLAlchemy, yaml serializer. ## Concurrency celery[eventlet] for using the eventlet pool. celery[gevent] for using the gevent pool. celery[threads] for using the thread pool. ## Transports and Backends celery[librabbitmq] degrade performance instead. Including the default prefork pool, Celery also supports using Eventlet, Gevent, and threads (see Concurrency). – Events is an option that when enabled causes Celery to send monitoring

RabbitMQ, Redis, Amazon SQS, and more... • Concurrency • prefork • (multiprocessing), • Eventlet, gevent • solo (single threaded) ## • Result Stores • AMQP, Redis • Memcached, • SQLAlchemy, Django yaml serializer. Concurrency celery[eventlet]: for using the eventlet pool. celery[gevent]: for using the gevent pool. Transports and Backends celery[librabbitmq]: for using the librabbitmq C library degrade performance instead. Including the default prefork pool, Celery also supports using Eventlet, Gevent, and running in a single thread (see Concurrency). – Events is an option that when enabled causes

RabbitMQ, Redis, Amazon SQS, and more... • Concurrency • prefork • (multiprocessing), • Eventlet, gevent • solo (single threaded) ## • Result Stores • AMQP, Redis • Memcached, • SQLAlchemy, Django yaml serializer. Concurrency celery[eventlet]: for using the eventlet pool. celery[gevent]: for using the gevent pool. Transports and Backends celery[librabbitmq]: for using the librabbitmq C library degrade performance instead. Including the default prefork pool, Celery also supports using Eventlet, Gevent, and running in a single thread (see Concurrency). – Events is an option that when enabled causes

RabbitMQ, Redis, Amazon SQS, and more... • Concurrency • prefork • (multiprocessing), • Eventlet, gevent • solo (single threaded) ## • Result Stores • AMQP, Redis • Memcached, • SQLAlchemy, Django yaml serializer. Concurrency celery[eventlet]: for using the eventlet pool. celery[gevent]: for using the gevent pool. Transports and Backends celery[librabbitmq]: for using the librabbitmq C library degrade performance instead. Including the default prefork pool, Celery also supports using Eventlet, Gevent, and running in a single thread (see Concurrency). – Events is an option that when enabled causes