concurrent web spider Structure of a Tornado web application Templates and UI Authentication and security Running and deploying Web framework tornado.web — RequestHandler and Application classes tornado development tornado.log — Logging support tornado.options — Command-line parsing tornado.stack_context — Exception handling across asynchronous callbacks tornado.testing — Unit testing support for asynchronous and UI Configuring templates Template syntax Internationalization UI modules Authentication and security Cookies and secure cookies User authentication Third party authentication Cross-site request forgery

can be blocking in some respects and non-blocking in others. In the context of Tornado we generally talk about blocking in the context of network I/O, although all kinds of blocking are to be minimized like gevent are sometimes called coroutines as well, but in Tornado all coroutines use explicit context switches and are called as asynchronous functions). Coroutines are almost as simple as synchronous thread. They also make concurrency easier to reason about by reducing the number of places where a context switch can happen. Example: async def fetch_coroutine(url): http_client = AsyncHTTPClient() response

concurrent web spider Structure of a Tornado web application Templates and UI Authentication and security Running and deploying Web framework tornado.web — RequestHandler and Application classes tornado Future objects tornado.log — Logging support tornado.options — Command-line parsing tornado.stack_context — Exception handling across asynchronous callbacks tornado.testing — Unit testing support for asynchronous and UI Configuring templates Template syntax Internationalization UI modules Authentication and security Cookies and secure cookies User authentication Third party authentication Cross-site request forgery

can be blocking in some respects and non-blocking in others. In the context of Tornado we generally talk about blocking in the context of network I/O, although all kinds of blocking are to be minimized like gevent are sometimes called coroutines as well, but in Tornado all coroutines use explicit context switches and are called as asynchronous functions). Coroutines are almost as simple as synchronous thread. They also make concurrency easier to reason about by reducing the number of places where a context switch can happen. Example: async def fetch_coroutine(url): http_client = AsyncHTTPClient() response

curl_httpclient with a properly-configured build of libcurl). In the context of Tornado we generally talk about blocking in the context of network I/O, although all kinds of blocking are to be minimized like gevent are sometimes called coroutines as well, but in Tornado all coroutines use explicit context switches and are called as asynchronous functions). Coroutines are almost as simple as synchronous thread. They also make concurrency easier to reason about by reducing the number of places where a context switch can happen. Example: from tornado import gen @gen.coroutine def fetch_coroutine(url): http_client

concurrent web spider Structure of a Tornado web application Templates and UI Authentication and security Running and deploying Web framework tornado.web — RequestHandler and Application classes tornado handlers Templates and UI Configuring templates Template syntax Security Internationalization UI modules Authentication and security Cookies and signed cookies User authentication Third party authentication can be blocking in some respects and non-blocking in others. In the context of Tornado we generally talk about blocking in the context of network I/O, although all kinds of blocking are to be minimized

can be blocking in some respects and non-blocking in others. In the context of Tornado we generally talk about blocking in the context of network I/O, although all kinds of blocking are to be minimized like gevent are sometimes called coroutines as well, but in Tornado all coroutines use explicit context switches and are called as asynchronous functions). Coroutines are almost as simple as synchronous thread. They also make concurrency easier to reason about by reducing the number of places where a context switch can happen. Example: async def fetch_coroutine(url): http_client = AsyncHTTPClient() response

can be blocking in some respects and non-blocking in others. In the context of Tornado we generally talk about blocking in the context of network I/O, although all kinds of blocking are to be minimized like gevent are sometimes called coroutines as well, but in Tornado all coroutines use explicit context switches and are called as asynchronous functions). Coroutines are almost as simple as synchronous thread. They also make concurrency easier to reason about by reducing the number of places where a context switch can happen. Example: async def fetch_coroutine(url): http_client = AsyncHTTPClient() response

can be blocking in some respects and non-blocking in others. In the context of Tornado we generally talk about blocking in the context of network I/O, although all kinds of blocking are to be minimized like gevent are sometimes called coroutines as well, but in Tornado all coroutines use explicit context switches and are called as asynchronous functions). Coroutines are almost as simple as synchronous thread. They also make concurrency easier to reason about by reducing the number of places where a context switch can happen. Example: async def fetch_coroutine(url): http_client = AsyncHTTPClient() response

can be blocking in some respects and non-blocking in others. In the context of Tornado we generally talk about blocking in the context of network I/O, although all kinds of blocking are to be minimized like gevent are sometimes called coroutines as well, but in Tornado all coroutines use explicit context switches and are called as asynchronous functions). Coroutines are almost as simple as synchronous thread. They also make concurrency easier to reason about by reducing the number of places where a context switch can happen. Example: async def fetch_coroutine(url): http_client = AsyncHTTPClient() response