tornado.tcpserver — Basic IOStream-based TCP server Coroutines and concurrency tornado.gen — Generator-based coroutines tornado.locks – Synchronization primitives tornado.queues – Queues for coroutines divided into four major components: A web framework (including RequestHandler which is subclassed to create web applications, and various supporting classes). Client- and server-side implementions of HTTP yield is a generator. All generators are asynchronous; when called they return a generator object instead of running to completion. The @gen.coroutine decorator communicates with the generator via the yield

tornado.tcpserver — Basic IOStream-based TCP server Coroutines and concurrency tornado.gen — Generator-based coroutines tornado.locks – Synchronization primitives tornado.queues – Queues for coroutines divided into four major components: A web framework (including RequestHandler which is subclassed to create web applications, and various supporting classes). Client- and server-side implementions of HTTP yield is a generator. All generators are asynchronous; when called they return a generator object instead of running to completion. The @gen.coroutine decorator communicates with the generator via the yield

tornado.tcpserver — Basic IOStream-based TCP server Coroutines and concurrency tornado.gen — Generator-based coroutines tornado.locks – Synchronization primitives tornado.queues – Queues for coroutines divided into four major components: A web framework (including RequestHandler which is subclassed to create web applications, and various supporting classes). Client- and server-side implementions of HTTP yield is a generator. All generators are asynchronous; when called they return a generator object instead of running to completion. The @gen.coroutine decorator communicates with the generator via the yield

divided into four major components: • A web framework (including RequestHandler which is subclassed to create web applications, and various supporting classes). • Client- and server-side implementions of HTTP yield is a generator. All generators are asynchronous; when called they return a generator object instead of running to completion. The @gen.coroutine decorator communicates with the generator via the yield decorator receives a Future from the generator, waits (without blocking) for that Future to complete, then “unwraps” the Future and sends the result back into the generator as the result of the yield expression

tornado.tcpserver — Basic IOStream-based TCP server Coroutines and concurrency tornado.gen — Generator-based coroutines tornado.locks – Synchronization primitives tornado.queues – Queues for coroutines divided into three major components: A web framework (including RequestHandler which is subclassed to create web applications, and various supporting classes). Client- and server-side implementions of HTTP yield is a generator. All generators are asynchronous; when called they return a generator object instead of running to completion. The @gen.coroutine decorator communicates with the generator via the yield

divided into four major components: • A web framework (including RequestHandler which is subclassed to create web applications, and various supporting classes). • Client- and server-side implementions of HTTP yield is a generator. All generators are asynchronous; when called they return a generator object instead of running to completion. The @gen.coroutine decorator communicates with the generator via the yield decorator receives a Future from the generator, waits (without blocking) for that Future to complete, then “unwraps” the Future and sends the result back into the generator as the result of the yield expression

divided into four major components: • A web framework (including RequestHandler which is subclassed to create web applications, and various supporting classes). • Client- and server-side implementions of HTTP yield is a generator. All generators are asynchronous; when called they return a generator object instead of running to completion. The @gen.coroutine decorator communicates with the generator via the yield decorator receives a Future from the generator, waits (without blocking) for that Future to complete, then “unwraps” the Future and sends the result back into the generator as the result of the yield expression

tornado.tcpserver — Basic IOStream-based TCP server Coroutines and concurrency tornado.gen — Generator-based coroutines tornado.locks – Synchronization primitives tornado.queues – Queues for coroutines divided into three major components: A web framework (including RequestHandler which is subclassed to create web applications, and various supporting classes). Client- and server-side implementions of HTTP yield is a generator. All generators are asynchronous; when called they return a generator object instead of running to completion. The @gen.coroutine decorator communicates with the generator via the yield

divided into four major components: A web framework (including RequestHandler which is subclassed to create web applications, and various supporting classes). Client- and server-side implementions of HTTP yield http_client.fetch(url) # In Python versions prior to 3.3, returning a value from # a generator is not allowed and you must use # raise gen.Return(response.body) # instead. return response yield is a generator. All generators are asynchronous; when called they return a generator object instead of running to completion. The @gen.coroutine decorator communicates with the generator via the yield

tornado.tcpserver — Basic IOStream-based TCP server Coroutines and concurrency tornado.gen — Generator-based coroutines tornado.locks – Synchronization primitives tornado.queues – Queues for coroutines divided into three major components: A web framework (including RequestHandler which is subclassed to create web applications, and various supporting classes). Client- and server-side implementions of HTTP yield is a generator. All generators are asynchronous; when called they return a generator object instead of running to completion. The @gen.coroutine decorator communicates with the generator via the yield