parameters. Something great for RPC, that you’d need to implement yourself the moment you need it. Transports: One of the main feature of Socket.IO is the abstraction of the transport, that gives you real-time native WebSockets when available to the browser, for even lower latencies. Currently supported transports: websocket, flashsocket, htmlfile, xhr-multipart, xhr-polling, jsonp-polling. This implementation come across the notion of a Socket. This is a virtual socket, that abstracts the fact that some transports are long-polling and others are stateful (like a Websocket), and exposes the same functionality

Celery requires a message transport to send and receive messages. The RabbitMQ and Redis broker transports are feature complete, but there’s also support for a myriad of other experimental solutions, including implementations, serializers, compression schemes, logging, schedulers, consumers, producers, broker transports, and much more. It supports • Brokers • RabbitMQ, Redis, • Amazon SQS, and more... • Concurrency 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. celery[redis] for using

Celery requires a message transport to send and receive messages. The RabbitMQ and Redis broker transports are feature complete, but there’s also support for a myriad of other experimental solutions, including implementations, serializers, compression schemes, logging, schedulers, consumers, producers, broker transports, and much more. It supports • Brokers • RabbitMQ, Redis, • Amazon SQS, and more... 2.2. Getting 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. celery[redis] for using

Celery requires a message transport to send and receive messages. The RabbitMQ and Redis broker transports are feature complete, but there’s also support for a myriad of other experimental solutions, including implementations, serializers, compression schemes, logging, schedulers, consumers, producers, broker transports, and much more. It supports • Brokers • RabbitMQ, Redis, • Amazon SQS, and more... 2.2. Getting 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. celery[redis] for using

Celery requires a message transport to send and receive messages. The RabbitMQ and Redis broker transports are feature complete, but there’s also support for a myriad of other experimental solutions, including implementations, serializers, compression schemes, logging, schedulers, consumers, producers, broker transports, and much more. It supports • Brokers • RabbitMQ, Redis, • Amazon SQS, and more... • Concurrency 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. celery[redis] for using

Celery requires a message transport to send and receive messages. The RabbitMQ and Redis broker transports are feature complete, but there’s also support for a myriad of other experimental solutions, including implementations, serializers, compression schemes, logging, schedulers, consumers, producers, broker transports, and much more. It supports • Brokers • RabbitMQ, Redis, • Amazon SQS, and more... 2.2. Getting 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. celery[redis] for using

Celery requires a message transport to send and receive messages. The RabbitMQ and Redis broker transports are feature complete, but there’s also support for a myriad of other experimental solutions, including implementations, serializers, compression schemes, logging, schedulers, consumers, producers, broker transports, and much more. It supports • Brokers • RabbitMQ, Redis, • Amazon SQS, and more... 2.2. Getting 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. celery[redis] for using

Celery requires a message transport to send and receive messages. The RabbitMQ and Redis broker transports are feature complete, but there’s also support for a myriad of other experimental solutions, including implementations, serializers, compression schemes, logging, schedulers, consumers, producers, broker transports, and much more. It supports • Brokers • RabbitMQ, Redis, • Amazon SQS, and more... 2.2. Getting 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. 10 Chapter 2. Contents

Celery requires a message transport to send and receive messages. The RabbitMQ and Redis broker transports are feature complete, but there’s also support for a myriad of other experimental solutions, including implementations, serializers, compression schemes, logging, schedulers, consumers, producers, broker transports, and much more. It supports • Brokers • RabbitMQ, Redis, • Amazon SQS, and more... 2.2. Getting 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. 10 Chapter 2. Contents

Celery requires a message transport to send and receive messages. The RabbitMQ and Redis broker transports are feature complete, but there’s also support for a myriad of other experimental solutions, including implementations, serializers, compression schemes, logging, schedulers, consumers, producers, broker transports, and much more. It supports • Brokers • RabbitMQ, Redis, • Amazon SQS, and more... 2.2. Getting 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. 10 Chapter 2. Contents