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() Take 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

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() Take 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

handler is running, any long-running handler should be made asynchronous so it can call its slow operations in a non-blocking way. This topic is covered in more detail in Asynchronous and non-Blocking I/O; 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.get_browser_l 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

handler is running, any long-running handler should be made asynchronous so it can call its slow operations in a non-blocking way. This topic is covered in more detail in Asynchronous and non-Blocking I/O; 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.get_browser_l 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

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() → tornado 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:

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() → tornado 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:

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() → tornado a ping frame is received. exception tornado.websocket.WebSocketClosedError[source] Raised by operations on a closed connection. New in version 3.2. Client-side support tornado.websocket.websocket_connect(url:

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() → tornado a ping frame is received. exception tornado.websocket.WebSocketClosedError[source] Raised by operations on a closed connection. New in version 3.2. Client-side support tornado.websocket.websocket_connect(url:

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 Tornado

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: