Tornado 6.1 Documentation
request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body class decorator. In the demos instance (even indirectly) before the fork. Second, it is difficult to do zero-downtime updates in this model. Finally, since all the processes share the same port it is more difficult to monitor them individually string or an iterator of byte strings. The latter is preferred for large files as it helps reduce memory fragmentation. 6.2. Web framework 57 Tornado Documentation, Release 6.1 New in version 3.1. classmethod0 码力 | 245 页 | 904.24 KB | 1 年前3
Tornado 6.0 Documentation
request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body class decorator. In the demos instance (even indirectly) before the fork. Second, it is difficult to do zero-downtime updates in this model. Finally, since all the processes share the same port it is more difficult to monitor them individually string or an iterator of byte strings. The latter is preferred for large files as it helps reduce memory fragmentation. New in version 3.1. 58 Chapter 6. Documentation Tornado Documentation, Release0 码力 | 245 页 | 885.76 KB | 1 年前3
Tornado 5.1 Documentation
request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body class decorator. In the demos instance (even indirectly) before the fork. Second, it is difficult to do zero-downtime updates in this model. Finally, since all the processes share the same port it is more difficult to monitor them individually string or an iterator of byte strings. The latter is preferred for large files as it helps reduce memory fragmentation. 56 Chapter 5. Documentation Tornado Documentation, Release 5.1.1 New in version0 码力 | 243 页 | 895.80 KB | 1 年前3
Tornado 4.5 Documentation
request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body class decorator. In the demos instance (even indirectly) before the fork. Second, it is difficult to do zero-downtime updates in this model. Finally, since all the processes share the same port it is more difficult to monitor them individually string or an iterator of byte strings. The latter is preferred for large files as it helps reduce memory fragmentation. New in version 3.1. classmethod get_content_version(abspath) Returns a version0 码力 | 333 页 | 322.34 KB | 1 年前3
Tornado 4.5 Documentation
request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body class decorator. In the demos instance (even indirectly) before the fork. Second, it is difficult to do zero-downtime updates in this model. Finally, since all the processes share the same port it is more difficult to monitor them individually string or an iterator of byte strings. The latter is preferred for large files as it helps reduce memory fragmentation. New in version 3.1. classmethod get_content_version(abspath) Returns a version0 码力 | 222 页 | 833.04 KB | 1 年前3
Tornado 6.4 Documentation
request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body class decorator. In the demos instance (even indirectly) before the fork. Second, it is difficult to do zero-downtime updates in this model. Finally, since all the processes share the same port it is more difficult to monitor them individually string or an iterator of byte strings. The latter is preferred for large files as it helps reduce memory fragmentation. New in version 3.1. classmethod get_content_version(abspath: str) → str Returns0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.4 Documentation
request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body class decorator. In the demos instance (even indirectly) before the fork. Second, it is difficult to do zero-downtime updates in this model. Finally, since all the processes share the same port it is more difficult to monitor them individually string or an iterator of byte strings. The latter is preferred for large files as it helps reduce memory fragmentation. New in version 3.1. classmethod get_content_version(abspath: str) → str Returns0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.4 Documentation
request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body class decorator. In the demos instance (even indirectly) before the fork. Second, it is difficult to do zero-downtime updates in this model. Finally, since all the processes share the same port it is more difficult to monitor them individually string or an iterator of byte strings. The latter is preferred for large files as it helps reduce memory fragmentation. New in version 3.1. classmethod get_content_version(abspath: str) → str Returns0 码力 | 268 页 | 1.09 MB | 1 年前3
Tornado 6.5 Documentationrequest.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body class decorator. In the demos instance (even indirectly) before the fork. Second, it is difficult to do zero-downtime updates in this model. Finally, since all the processes share the same port it is more difficult to monitor them individually string or an iterator of byte strings. The latter is preferred for large files as it helps reduce memory fragmentation. Added in version 3.1. classmethod get_content_version(abspath: str) → str Returns0 码力 | 272 页 | 1.12 MB | 3 月前3
Tornado 6.2 Documentation
request.body. By default uploaded files are fully buffered in memory; if you need to handle files that are too large to comfortably keep in memory see the stream_request_body class decorator. In the demos instance (even indirectly) before the fork. Second, it is difficult to do zero-downtime updates in this model. Finally, since all the processes share the same port it is more difficult to monitor them individually string or an iterator of byte strings. The latter is preferred for large files as it helps reduce memory fragmentation. New in version 3.1. classmethod get_content_version(abspath: str) → str Returns0 码力 | 260 页 | 1.06 MB | 1 年前3
共 20 条
- 1
- 2













