Tornado 6.5 Documentationweb) directly instead of using WSGI. In general, Tornado code is not thread-safe. The only method in Tornado that is safe to call from other threads is IOLoop.add_callback. You can also use IOLoop.run_in_executor Thread-safety notes In general, methods on RequestHandler and elsewhere in Tornado are not thread-safe. In particular, methods such as write(), finish(), and flush() must only be called from the main thread version 3.2.2: The xsrf token will now be have a random mask applied in every request, which makes it safe to include the token in pages that are compressed. See http://breachattack.com for more information0 码力 | 272 页 | 1.12 MB | 3 月前3
Tornado 6.5 Documentationweb) directly instead of using WSGI. In general, Tornado code is not thread-safe. The only method in Tornado that is safe to call from other threads is IOLoop.add_callback. You can also use IOLoop.run_in_executor Thread-safety notes In general, methods on RequestHandler and elsewhere in Tornado are not thread-safe. In particular, methods such as write(), finish(), and flush() must only be called from the main thread version 3.2.2: The xsrf token will now be have a random mask applied in every request, which makes it safe to include the token in pages that are compressed. See http://breachattack.com for more information0 码力 | 437 页 | 405.14 KB | 3 月前3
julia 1.13.0 DEVTask Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 25.9 Safe use of Finalizers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 26 Multi-processing since convert can be called implicitly, its methods are restricted to cases that are considered "safe" or "unsurprising". convert will only convert between types that repre- sent the same basic kind Finally, it takes account of changes in any compile-time preferences. If you know that a module is not safe to precompile (for example, for one of the reasons described below), you should put __precompile__(false)0 码力 | 2058 页 | 7.45 MB | 3 月前3
Julia 1.12.0 RC1Task Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 25.9 Safe use of Finalizers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 26 Multi-processing since convert can be called implicitly, its methods are restricted to cases that are considered "safe" or "unsurprising". convert will only convert between types that repre- sent the same basic kind Finally, it takes account of changes in any compile-time preferences. If you know that a module is not safe to precompile (for example, for one of the reasons described below), you should put __precompile__(false)0 码力 | 2057 页 | 7.44 MB | 3 月前3
Julia 1.12.0 Beta4Task Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 25.9 Safe use of Finalizers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 26 Multi-processing since convert can be called implicitly, its methods are restricted to cases that are considered "safe" or "unsurprising". convert will only convert between types that repre- sent the same basic kind Finally, it takes account of changes in any compile-time preferences. If you know that a module is not safe to precompile (for example, for one of the reasons described below), you should put __precompile__(false)0 码力 | 2057 页 | 7.44 MB | 3 月前3
Julia 1.12.0 Beta3Task Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 25.9 Safe use of Finalizers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 26 Multi-processing since convert can be called implicitly, its methods are restricted to cases that are considered "safe" or "unsurprising". convert will only convert between types that repre- sent the same basic kind Finally, it takes account of changes in any compile-time preferences. If you know that a module is not safe to precompile (for example, for one of the reasons described below), you should put __precompile__(false)0 码力 | 2057 页 | 7.44 MB | 3 月前3
julia 1.10.10Task Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 24.11 Safe use of Finalizers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 25 Multi-processing since convert can be called implicitly, its methods are restricted to cases that are considered "safe" or "unsurprising". convert will only convert between types that repre- sent the same basic kind Finally, it takes account of changes in any compile-time preferences. If you know that a module is not safe to precompile (for example, for one of the reasons described below), you should put __precompile__(false)0 码力 | 1692 页 | 6.34 MB | 3 月前3
Julia 1.11.6 Release NotesTask Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 25.9 Safe use of Finalizers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 26 Multi-processing since convert can be called implicitly, its methods are restricted to cases that are considered "safe" or "unsurprising". convert will only convert between types that repre- sent the same basic kind Finally, it takes account of changes in any compile-time preferences. If you know that a module is not safe to precompile (for example, for one of the reasons described below), you should put __precompile__(false)0 码力 | 2007 页 | 6.73 MB | 3 月前3
julia 1.12.0 beta1Task Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 25.9 Safe use of Finalizers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 26 Multi-processing since convert can be called implicitly, its methods are restricted to cases that are considered "safe" or "unsurprising". convert will only convert between types that repre- sent the same basic kind Finally, it takes account of changes in any compile-time preferences. If you know that a module is not safe to precompile (for example, for one of the reasons described below), you should put __precompile__(false)0 码力 | 2047 页 | 7.41 MB | 3 月前3
Julia 1.10.9Task Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 24.11 Safe use of Finalizers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 25 Multi-processing since convert can be called implicitly, its methods are restricted to cases that are considered "safe" or "unsurprising". convert will only convert between types that repre- sent the same basic kind Finally, it takes account of changes in any compile-time preferences. If you know that a module is not safe to precompile (for example, for one of the reasons described below), you should put __precompile__(false)0 码力 | 1692 页 | 6.34 MB | 3 月前3
共 20 条
- 1
- 2













