index modules | gevent-socketio 0.3.1 documentation » Gevent-socketio documentation Introduction Socket.IO is a WebSocket-like abstraction that enables real-time communication between a browser and and a server. gevent-socketio is a Python implementation of the protocol. The reference server implementation of Socket.IO runs on Node.js and was developed by LearnBoost. There are now server implementations 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 Documentation Release 0.3.1 Jeffrey Gelens,Alex Bourget,John Anderson March 19, 2015 Contents 1 Introduction 1 2 Concepts 3 3 Getting started 5 4 Examples 7 5 Security 9 6 API 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 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

Brokers RabbitMQ, Redis, Amazon SQS, and more… Concurrency prefork (multiprocessing), Eventlet, gevent solo (single threaded) Result Stores AMQP, Redis Memcached, SQLAlchemy, Django ORM Apache Cassandra 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

Django ORM (exp), Amazon SQS, (exp) and more… Concurrency prefork (multiprocessing), Eventlet, gevent threads/single threaded Result Stores AMQP, Redis memcached, MongoDB SQLAlchemy, Django ORM Apache 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

Brokers RabbitMQ, Redis, Amazon SQS, and more… Concurrency prefork (multiprocessing), Eventlet, gevent solo (single threaded) Result Stores AMQP, Redis Memcached, SQLAlchemy, Django ORM Apache Cassandra 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

Brokers RabbitMQ, Redis, Amazon SQS, and more… Concurrency prefork (multiprocessing), Eventlet, gevent solo (single threaded) Result Stores AMQP, Redis Memcached, SQLAlchemy, Django ORM Apache Cassandra 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

Brokers RabbitMQ, Redis, Amazon SQS, and more… Concurrency prefork (multiprocessing), Eventlet, gevent solo (single threaded) Result Stores AMQP, Redis Memcached, SQLAlchemy, Django ORM Apache Cassandra 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

ORM (exp), Amazon SQS, (exp) • and more... • Concurrency • prefork (multiprocessing), • Eventlet, gevent 2.2. Getting Started 7 Celery Documentation, Release 3.1.25 • threads/single threaded • Result the yaml serializer. Concurrency celery[eventlet] for using the eventlet pool. celery[gevent] for using the gevent pool. celery[threads] for using the thread pool. 10 Chapter 2. Contents Celery Documentation 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

Brokers RabbitMQ, Redis, Amazon SQS, and more… Concurrency prefork (multiprocessing), Eventlet, gevent solo (single threaded) Result Stores AMQP, Redis Memcached, SQLAlchemy, Django ORM Apache Cassandra worker queues at runtime celery[auth]: celery[msgpack]: celery[yaml]: celery[eventlet]: celery[gevent]: get the id of the current task Jump to ⟶ Brokers Applications Tasks Calling Workers Daemonizing using the eventlet [https://pypi.python.org/pypi/eventlet/] pool. for using the gevent [https://pypi.python.org/pypi/gevent/] pool. celery[librabbitmq]: celery[redis]: celery[sqs]: celery[tblib]: celery[memcache]: