WebSockets [https://en.wikipedia.org/wiki/WebSocket], and other applications that require a long-lived connection to each user. Quick links Current version: 6.1 (download from PyPI [https://pypi.python.org/pypi/tornado] httpclient — Asynchronous HTTP client tornado.httputil — Manipulate HTTP headers and URLs tornado.http1connection – HTTP/1.x client/server implementation Asynchronous networking tornado.ioloop — Main event loop non-blocking sockets tornado.netutil — Miscellaneous network utilities tornado.tcpclient — IOStream connection factory tornado.tcpserver — Basic IOStream-based TCP server Coroutines and concurrency tornado

WebSockets [http://en.wikipedia.org/wiki/WebSocket], and other applications that require a long-lived connection to each user. Quick links Current version: 6.0.4 (download from PyPI [https://pypi.python.org/pypi/tornado] httpclient — Asynchronous HTTP client tornado.httputil — Manipulate HTTP headers and URLs tornado.http1connection – HTTP/1.x client/server implementation Asynchronous networking tornado.ioloop — Main event loop non-blocking sockets tornado.netutil — Miscellaneous network utilities tornado.tcpclient — IOStream connection factory tornado.tcpserver — Basic IOStream-based TCP server Coroutines and concurrency tornado

making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. Contents 1 Tornado Documentation, Release 6.1 2 Contents CHAPTER 1 Quick links making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. Tornado can be roughly divided into four major components: • A web framework (including 1.2 Asynchronous and non-Blocking I/O Real-time web features require a long-lived mostly-idle connection per user. In a traditional synchronous web server, this implies devoting one thread to each user

making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. Contents 1 Tornado Documentation, Release 5.1.1 2 Contents CHAPTER 1 Quick links making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. Tornado can be roughly divided into four major components: • A web framework (including 1.2 Asynchronous and non-Blocking I/O Real-time web features require a long-lived mostly-idle connection per user. In a traditional synchronous web server, this implies devoting one thread to each user

making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. CONTENTS 1 Tornado Documentation, Release 6.0.4 2 CONTENTS CHAPTER ONE QUICK making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. Tornado can be roughly divided into four major components: • A web framework (including 1.2 Asynchronous and non-Blocking I/O Real-time web features require a long-lived mostly-idle connection per user. In a traditional synchronous web server, this implies devoting one thread to each user

making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. CONTENTS 1Tornado Documentation, Release 6.5.1 2 CONTENTSCHAPTER ONE QUICK LINKS making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. Tornado can be roughly divided into three major components: • A web framework (including 1.2 Asynchronous and non-Blocking I/O Real-time web features require a long-lived mostly-idle connection per user. In a traditional synchronous web server, this implies devoting one thread to each user

making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. CONTENTS 1 Tornado Documentation, Release 6.4 2 CONTENTS CHAPTER ONE QUICK making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. Tornado can be roughly divided into three major components: • A web framework (including 1.2 Asynchronous and non-Blocking I/O Real-time web features require a long-lived mostly-idle connection per user. In a traditional synchronous web server, this implies devoting one thread to each user

making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. CONTENTS 1 Tornado Documentation, Release 6.4 2 CONTENTS CHAPTER ONE QUICK making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. Tornado can be roughly divided into three major components: • A web framework (including 1.2 Asynchronous and non-Blocking I/O Real-time web features require a long-lived mostly-idle connection per user. In a traditional synchronous web server, this implies devoting one thread to each user

making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. CONTENTS 1 Tornado Documentation, Release 6.4 2 CONTENTS CHAPTER ONE QUICK making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. Tornado can be roughly divided into three major components: • A web framework (including 1.2 Asynchronous and non-Blocking I/O Real-time web features require a long-lived mostly-idle connection per user. In a traditional synchronous web server, this implies devoting one thread to each user

making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. CONTENTS 1 Tornado Documentation, Release 6.3.3 2 CONTENTS CHAPTER ONE QUICK making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. Tornado can be roughly divided into three major components: • A web framework (including 1.2 Asynchronous and non-Blocking I/O Real-time web features require a long-lived mostly-idle connection per user. In a traditional synchronous web server, this implies devoting one thread to each user