Tornado 4.5 Documentation
server, this implies devoting one thread to each user, which can be very expensive. To minimize the cost of concurrent connections, Tornado uses a single-threaded event loop. This means that all application still open, and the response is finally flushed to the client with the call to self.finish(). For comparison, here is the same example using a coroutine: class MainHandler(tornado.web.RequestHandler):0 码力 | 333 页 | 322.34 KB | 1 年前3
Tornado 4.5 Documentation
each user, which can be very expensive. 9 Tornado Documentation, Release 4.5.3 To minimize the cost of concurrent connections, Tornado uses a single-threaded event loop. This means that all application still open, and the response is finally flushed to the client with the call to self.finish(). For comparison, here is the same example using a coroutine: class MainHandler(tornado.web.RequestHandler): @tornado0 码力 | 222 页 | 833.04 KB | 1 年前3- Tornado 6.0 Documentation
server, this implies devoting one thread to each user, which can be very expensive. To minimize the cost of concurrent connections, Tornado uses a single-threaded event loop. This means that all application # Inline the first iteration of Runner.run. This lets us # avoid the cost of creating a Runner when the coroutine # never actually yields, which in turn allows deadline, next(io_loop._timeout_counter), ) # type: Tuple[float, int] # Comparison methods to sort by deadline, with object id as a tiebreaker # to guarantee a consistent ordering0 码力 | 869 页 | 692.83 KB | 1 年前3
- Tornado 6.1 Documentation
server, this implies devoting one thread to each user, which can be very expensive. To minimize the cost of concurrent connections, Tornado uses a single-threaded event loop. This means that all application # Inline the first iteration of Runner.run. This lets us # avoid the cost of creating a Runner when the coroutine # never actually yields, which in turn allows deadline, next(io_loop._timeout_counter), ) # type: Tuple[float, int] # Comparison methods to sort by deadline, with object id as a tiebreaker # to guarantee a consistent ordering0 码力 | 931 页 | 708.03 KB | 1 年前3
- Tornado 6.1 Documentation
server, this implies devoting one thread to each user, which can be very expensive. To minimize the cost of concurrent connections, Tornado uses a single-threaded event loop. This means that all application0 码力 | 245 页 | 904.24 KB | 1 年前3
- Tornado 5.1 Documentation
server, this implies devoting one thread to each user, which can be very expensive. To minimize the cost of concurrent connections, Tornado uses a single-threaded event loop. This means that all application0 码力 | 243 页 | 895.80 KB | 1 年前3
- Tornado 6.0 Documentation
server, this implies devoting one thread to each user, which can be very expensive. To minimize the cost of concurrent connections, Tornado uses a single-threaded event loop. This means that all application0 码力 | 245 页 | 885.76 KB | 1 年前3
- Tornado 6.4 Documentation
server, this implies devoting one thread to each user, which can be very expensive. To minimize the cost of concurrent connections, Tornado uses a single-threaded event loop. This means that all appli- cation0 码力 | 268 页 | 1.09 MB | 1 年前3
- Tornado 6.2 Documentation
server, this implies devoting one thread to each user, which can be very expensive. To minimize the cost of concurrent connections, Tornado uses a single-threaded event loop. This means that all appli- cation0 码力 | 260 页 | 1.06 MB | 1 年前3
- Tornado 6.4 Documentation
server, this implies devoting one thread to each user, which can be very expensive. To minimize the cost of concurrent connections, Tornado uses a single-threaded event loop. This means that all appli- cation0 码力 | 268 页 | 1.09 MB | 1 年前3
共 20 条
- 1
- 2