Tornado 6.4 Documentation
comparable to asynchronous systems, but they do not actually make things asynchronous). Asynchronous operations in Tornado generally return placeholder objects (Futures), with the exception of some low- level get_current_user() may not, so the latter form is necessary if loading the user requires asynchronous operations. The user object may be any type of the application’s choosing. RequestHandler.detach() → IOStream response to a ping frame is received. exception tornado.websocket.WebSocketClosedError Raised by operations on a closed connection. New in version 3.2. Client-side support 6.2. Web framework 81 Tornado0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.2 Documentation
comparable to asynchronous systems, but they do not actually make things asynchronous). Asynchronous operations in Tornado generally return placeholder objects (Futures), with the exception of some low- level get_current_user() may not, so the latter form is necessary if loading the user requires asynchronous operations. The user object may be any type of the application’s choosing. RequestHandler.detach() → IOStream response to a ping frame is received. exception tornado.websocket.WebSocketClosedError Raised by operations on a closed connection. New in version 3.2. Client-side support tornado.websocket.websocket_connect(url:0 码力 | 260 页 | 1.06 MB | 1 年前3
Tornado 6.4 Documentation
comparable to asynchronous systems, but they do not actually make things asynchronous). Asynchronous operations in Tornado generally return placeholder objects (Futures), with the exception of some low- level get_current_user() may not, so the latter form is necessary if loading the user requires asynchronous operations. The user object may be any type of the application’s choosing. RequestHandler.detach() → IOStream response to a ping frame is received. exception tornado.websocket.WebSocketClosedError Raised by operations on a closed connection. New in version 3.2. Client-side support 6.2. Web framework 81 Tornado0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.4 Documentation
comparable to asynchronous systems, but they do not actually make things asynchronous). Asynchronous operations in Tornado generally return placeholder objects (Futures), with the exception of some low- level get_current_user() may not, so the latter form is necessary if loading the user requires asynchronous operations. The user object may be any type of the application’s choosing. RequestHandler.detach() → IOStream response to a ping frame is received. exception tornado.websocket.WebSocketClosedError Raised by operations on a closed connection. New in version 3.2. Client-side support 6.2. Web framework 81 Tornado0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.3 Documentation
comparable to asynchronous systems, but they do not actually make things asynchronous). Asynchronous operations in Tornado generally return placeholder objects (Futures), with the exception of some low- level get_current_user() may not, so the latter form is necessary if loading the user requires asynchronous operations. The user object may be any type of the application’s choosing. RequestHandler.detach() → IOStream response to a ping frame is received. exception tornado.websocket.WebSocketClosedError Raised by operations on a closed connection. New in version 3.2. Client-side support tornado.websocket.websocket_connect(url:0 码力 | 264 页 | 1.06 MB | 1 年前3
Tornado 6.5 Documentationcomparable to asynchronous systems, but they do not actually make things asynchronous). Asynchronous operations in Tornado generally return placeholder objects (Futures), with the exception of some low- level get_current_user() may not, so the latter form is necessary if loading the user requires asynchronous operations. The user object may be any type of the application’s choosing. RequestHandler.detach() → IOStream response to a ping frame is received. exception tornado.websocket.WebSocketClosedError Raised by operations on a closed connection. Added in version 3.2. Client-side support tornado.websocket.websocket_connect(url:0 码力 | 272 页 | 1.12 MB | 3 月前3
Tornado 6.2 Documentation
comparable to asynchronous systems, but they do not actually make things asynchronous). Asynchronous operations in Tornado generally return placeholder objects (Futures), with the exception of some low-level get_current_user() may not, so the latter form is necessary if loading the user requires asynchronous operations. The user object may be any type of the application’s choosing. RequestHandler.detach() → IOStream response to a ping frame is received. exception tornado.websocket.WebSocketClosedError Raised by operations on a closed connection. New in version 3.2. Client-side support tornado.websocket.websocket_connect(url:0 码力 | 407 页 | 385.03 KB | 1 年前3
Tornado 6.4 Documentation
comparable to asynchronous systems, but they do not actually make things asynchronous). Asynchronous operations in Tornado generally return placeholder objects (Futures), with the exception of some low-level get_current_user() may not, so the latter form is necessary if loading the user requires asynchronous operations. The user object may be any type of the application’s choosing. RequestHandler.detach() → IOStream response to a ping frame is received. exception tornado.websocket.WebSocketClosedError Raised by operations on a closed connection. New in version 3.2. Client-side support tornado.websocket.websocket_connect(url:0 码力 | 432 页 | 402.58 KB | 1 年前3
Tornado 6.4 Documentation
comparable to asynchronous systems, but they do not actually make things asynchronous). Asynchronous operations in Tornado generally return placeholder objects (Futures), with the exception of some low-level get_current_user() may not, so the latter form is necessary if loading the user requires asynchronous operations. The user object may be any type of the application’s choosing. RequestHandler.detach() → IOStream response to a ping frame is received. exception tornado.websocket.WebSocketClosedError Raised by operations on a closed connection. New in version 3.2. Client-side support tornado.websocket.websocket_connect(url:0 码力 | 432 页 | 402.58 KB | 1 年前3
Tornado 6.4 Documentation
comparable to asynchronous systems, but they do not actually make things asynchronous). Asynchronous operations in Tornado generally return placeholder objects (Futures), with the exception of some low-level get_current_user() may not, so the latter form is necessary if loading the user requires asynchronous operations. The user object may be any type of the application’s choosing. RequestHandler.detach() → IOStream response to a ping frame is received. exception tornado.websocket.WebSocketClosedError Raised by operations on a closed connection. New in version 3.2. Client-side support tornado.websocket.websocket_connect(url:0 码力 | 432 页 | 402.58 KB | 1 年前3
共 20 条
- 1
- 2













