that require a long-lived connection to each user. Tornado can be roughly divided into four major components: • A web framework (including RequestHandler which is subclassed to create web applications, and library including the classes IOLoop and IOStream, which serve as the building blocks for the HTTP components and can also be used to implement other protocols. • A coroutine library (tornado.gen) which allows in Tornado generally return placeholder objects (Futures), with the exception of some low-level components like the IOLoop that use callbacks. Futures are usually transformed into their result with the

that require a long-lived connection to each user. Tornado can be roughly divided into four major components: • A web framework (including RequestHandler which is subclassed to create web applications, and library including the classes IOLoop and IOStream, which serve as the building blocks for the HTTP components and can also be used to implement other protocols. • A coroutine library (tornado.gen) which allows in Tornado generally return placeholder objects (Futures), with the exception of some low-level components like the IOLoop that use callbacks. Futures are usually transformed into their result with the

that require a long-lived connection to each user. Tornado can be roughly divided into four major components: • A web framework (including RequestHandler which is subclassed to create web applications, and library including the classes IOLoop and IOStream, which serve as the building blocks for the HTTP components and can also be used to implement other protocols. • A coroutine library (tornado.gen) which allows in Tornado generally return placeholder objects (Futures), with the exception of some low-level components like the IOLoop that use callbacks. Futures are usually transformed into their result with the

Coroutines Queue example - a concurrent web spider Structure of a Tornado web application Templates and UI Authentication and security Running and deploying Web framework tornado.web — RequestHandler and methods Error Handling Redirection Asynchronous handlers Templates and UI Configuring templates Template syntax Internationalization UI modules Authentication and security Cookies and secure cookies User that require a long-lived connection to each user. Tornado can be roughly divided into four major components: A web framework (including RequestHandler which is subclassed to create web applications, and

require a long-lived connection to each user. Tornado can be roughly divided into three major components: • A web framework (including RequestHandler which is subclassed to create web applications, and library including the classes IOLoop and IOStream, which serve as the building blocks for the HTTP components and can also be used to implement other protocols. The Tornado web framework and HTTP server together in Tornado generally return placeholder objects (Futures), with the exception of some low- level components like the IOLoop that use callbacks. Futures are usually transformed into their result with the

require a long-lived connection to each user. Tornado can be roughly divided into three major components: • A web framework (including RequestHandler which is subclassed to create web applications, and library including the classes IOLoop and IOStream, which serve as the building blocks for the HTTP components and can also be used to implement other protocols. The Tornado web framework and HTTP server together in Tornado generally return placeholder objects (Futures), with the exception of some low- level components like the IOLoop that use callbacks. Futures are usually transformed into their result with the

require a long-lived connection to each user. Tornado can be roughly divided into three major components: • A web framework (including RequestHandler which is subclassed to create web applications, and library including the classes IOLoop and IOStream, which serve as the building blocks for the HTTP components and can also be used to implement other protocols. The Tornado web framework and HTTP server together in Tornado generally return placeholder objects (Futures), with the exception of some low- level components like the IOLoop that use callbacks. Futures are usually transformed into their result with the

require a long-lived connection to each user. Tornado can be roughly divided into three major components: • A web framework (including RequestHandler which is subclassed to create web applications, and library including the classes IOLoop and IOStream, which serve as the building blocks for the HTTP components and can also be used to implement other protocols. The Tornado web framework and HTTP server together in Tornado generally return placeholder objects (Futures), with the exception of some low- level components like the IOLoop that use callbacks. Futures are usually transformed into their result with the

require a long-lived connection to each user. Tornado can be roughly divided into three major components: • A web framework (including RequestHandler which is subclassed to create web applications, and library including the classes IOLoop and IOStream, which serve as the building blocks for the HTTP components and can also be used to implement other protocols. The Tornado web framework and HTTP server together in Tornado generally return placeholder objects (Futures), with the exception of some low- level components like the IOLoop that use callbacks. Futures are usually transformed into their result with the

require a long-lived connection to each user. Tornado can be roughly divided into three major components: • A web framework (including RequestHandler which is subclassed to create web applications, and library including the classes IOLoop and IOStream, which serve as the building blocks for the HTTP components and can also be used to implement other protocols. The Tornado web framework and HTTP server together in Tornado generally return placeholder objects (Futures), with the exception of some low- level components like the IOLoop that use callbacks. Futures are usually transformed into their result with the