Tornado 6.0 Documentation
handle streamed request data. Requires the stream_request_body decorator. May be a coroutine for flow control. Output RequestHandler.set_status(status_code: int, reason: str = None) → None Sets the example, this is the place to set a custom Server header. Note that setting such headers in the normal flow of request processing may not do what you want, since headers may be reset during error handling. framework 43 Tornado Documentation, Release 6.0.4 The callback argument, if given, can be used for flow control: it will be run when all flushed data has been written to the socket. Note that only one flush0 码力 | 245 页 | 885.76 KB | 1 年前3
Tornado 6.1 Documentation
handle streamed request data. Requires the stream_request_body decorator. May be a coroutine for flow control. Output RequestHandler.set_status(status_code: int, reason: Optional[str] = None) → None example, this is the place to set a custom Server header. Note that setting such headers in the normal flow of request processing may not do what you want, since headers may be reset during error handling. connection is already closed, raises WebSocketClosedError. Returns a Future which can be used for flow control. 74 Chapter 6. Documentation Tornado Documentation, Release 6.1 Changed in version 3.2:0 码力 | 245 页 | 904.24 KB | 1 年前3
Tornado 6.4 Documentation
handle streamed request data. Requires the stream_request_body decorator. May be a coroutine for flow control. 6.2. Web framework 43 Tornado Documentation, Release 6.4 Output RequestHandler.set_status(status_code: example, this is the place to set a custom Server header. Note that setting such headers in the normal flow of request processing may not do what you want, since headers may be reset during error handling. connection is already closed, raises WebSocketClosedError. Returns a Future which can be used for flow control. 6.2. Web framework 79 Tornado Documentation, Release 6.4 Changed in version 3.2: WebSocketClosedError0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.2 Documentation
handle streamed request data. Requires the stream_request_body decorator. May be a coroutine for flow control. Output RequestHandler.set_status(status_code: int, reason: Optional[str] = None) → None example, this is the place to set a custom Server header. Note that setting such headers in the normal flow of request processing may not do what you want, since headers may be reset during error handling. connection is already closed, raises WebSocketClosedError. Returns a Future which can be used for flow control. Changed in version 3.2: WebSocketClosedError was added (previously a closed connection would0 码力 | 260 页 | 1.06 MB | 1 年前3
Tornado 6.4 Documentation
handle streamed request data. Requires the stream_request_body decorator. May be a coroutine for flow control. 6.2. Web framework 43 Tornado Documentation, Release 6.4 Output RequestHandler.set_status(status_code: example, this is the place to set a custom Server header. Note that setting such headers in the normal flow of request processing may not do what you want, since headers may be reset during error handling. connection is already closed, raises WebSocketClosedError. Returns a Future which can be used for flow control. 6.2. Web framework 79 Tornado Documentation, Release 6.4 Changed in version 3.2: WebSocketClosedError0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.4 Documentation
handle streamed request data. Requires the stream_request_body decorator. May be a coroutine for flow control. 6.2. Web framework 43 Tornado Documentation, Release 6.4 Output RequestHandler.set_status(status_code: example, this is the place to set a custom Server header. Note that setting such headers in the normal flow of request processing may not do what you want, since headers may be reset during error handling. connection is already closed, raises WebSocketClosedError. Returns a Future which can be used for flow control. 6.2. Web framework 79 Tornado Documentation, Release 6.4 Changed in version 3.2: WebSocketClosedError0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.3 Documentation
handle streamed request data. Requires the stream_request_body decorator. May be a coroutine for flow control. 6.2. Web framework 43 Tornado Documentation, Release 6.3.3 Output RequestHandler.set example, this is the place to set a custom Server header. Note that setting such headers in the normal flow of request processing may not do what you want, since headers may be reset during error handling. connection is already closed, raises WebSocketClosedError. Returns a Future which can be used for flow control. Changed in version 3.2: WebSocketClosedError was added (previously a closed connection would0 码力 | 264 页 | 1.06 MB | 1 年前3
Tornado 6.5 Documentationhandle streamed request data. Requires the stream_request_body decorator. May be a coroutine for flow control. Output RequestHandler.set_status(status_code: int, reason: str | None = None) → None Sets example, this is the place to set a custom Server header. Note that setting such headers in the normal flow of request processing may not do what you want, since headers may be reset during error handling. connection is already closed, raises WebSocketClosedError. Returns a Future which can be used for flow control. Changed in version 3.2: WebSocketClosedError was added (previously a closed connection would0 码力 | 272 页 | 1.12 MB | 3 月前3
Tornado 6.0 Documentation
handle streamed request data. Requires the stream_request_body decorator. May be a coroutine for flow control. Output RequestHandler.set_status(status_code: int, reason: str = None) → None[source] example, this is the place to set a custom Server header. Note that setting such headers in the normal flow of request processing may not do what you want, since headers may be reset during error handling. Flushes the current output buffer to the network. The callback argument, if given, can be used for flow control: it will be run when all flushed data has been written to the socket. Note that only one flush0 码力 | 869 页 | 692.83 KB | 1 年前3
Tornado 5.1 Documentation
example, this is the place to set a custom Server header. Note that setting such headers in the normal flow of request processing may not do what you want, since headers may be reset during error handling. Flushes the current output buffer to the network. The callback argument, if given, can be used for flow control: it will be run when all flushed data has been written to the socket. Note that only one flush connection is already closed, raises WebSocketClosedError. Returns a Future which can be used for flow control. Changed in version 3.2: WebSocketClosedError was added (previously a closed connection would0 码力 | 243 页 | 895.80 KB | 1 年前3
共 20 条
- 1
- 2













