Python 标准库参考指南 2.7.18
created a database . . . . . . . . . . . . . . . . . . . . . . . 320 11.8 dbm —Simple “database”interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 11.9 gdbm —GNU’s reinterpretation . . . . . . . . 322 11.10 dbhash —DBM-style interface to the BSD database library . . . . . . . . . . . . . . . . . . . . . . 323 11.11 bsddb —Interface to Berkeley DB library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601 16.2 threading —Higher-level threading interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606 16.3 thread —Multiple threads of0 码力 | 1552 页 | 7.42 MB | 9 月前3Python 标准库参考指南 2.7.18
created a database . . . . . . . . . . . . . . . . . . . . . . . 320 11.8 dbm —Simple “database”interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 11.9 gdbm —GNU’s reinterpretation . . . . . . . . 322 11.10 dbhash —DBM-style interface to the BSD database library . . . . . . . . . . . . . . . . . . . . . . 323 11.11 bsddb —Interface to Berkeley DB library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601 16.2 threading —Higher-level threading interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606 16.3 thread —Multiple threads of0 码力 | 1552 页 | 7.42 MB | 9 月前3Python 标准库参考指南 2.7.18
created a database . . . . . . . . . . . . . . . . . . . . . . . 320 11.8 dbm —Simple “database”interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 11.9 gdbm —GNU’s reinterpretation . . . . . . . . 322 11.10 dbhash —DBM-style interface to the BSD database library . . . . . . . . . . . . . . . . . . . . . . 323 11.11 bsddb —Interface to Berkeley DB library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601 16.2 threading —Higher-level threading interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606 16.3 thread —Multiple threads of0 码力 | 1552 页 | 7.42 MB | 9 月前3Tornado 4.5 Documentation
officially supported and is recommended only for development use. Without reworking Tornado IOLoop interface, it’s not possible to add a native Tornado Windows IOLoop implementation or leverage Windows’ IOCP Deferred) Deliver to a queue Callback registry (e.g. POSIX signals) Regardless of which type of interface is used, asynchronous functions by definition interact differently with their callers; there is class can match on more criteria than Application, or the Router interface can be subclassed for maximum customization. Router interface extends HTTPServerConnectionDelegate to provide additional routing0 码力 | 333 页 | 322.34 KB | 1 年前3Tornado 4.5 Documentation
officially supported and is recommended only for development use. Without reworking Tornado IOLoop interface, it’s not possible to add a native Tornado Windows IOLoop implementation or leverage Windows’ IOCP Deferred) • Deliver to a queue • Callback registry (e.g. POSIX signals) Regardless of which type of interface is used, asynchronous functions by definition interact differently with their callers; there is class can match on more criteria than Application, or the Router interface can be subclassed for maximum customization. Router interface extends HTTPServerConnectionDelegate to provide additional routing0 码力 | 222 页 | 833.04 KB | 1 年前3Tornado 5.1 Documentation
officially supported and is recommended only for development use. Without reworking Tornado IOLoop interface, it’s not possible to add a native Tornado Windows IOLoop implementation or leverage Windows’ IOCP Deferred) • Deliver to a queue • Callback registry (e.g. POSIX signals) Regardless of which type of interface is used, asynchronous functions by definition interact differently with their callers; there is class can match on more criteria than Application, or the Router interface can be subclassed for maximum customization. Router interface extends HTTPServerConnectionDelegate to provide additional routing0 码力 | 243 页 | 895.80 KB | 1 年前3Tornado 5.1 Documentation
officially supported and is recommended only for development use. Without reworking Tornado IOLoop interface, it’s not possible to add a native Tornado Windows IOLoop implementation or leverage Windows’ IOCP Deferred) Deliver to a queue Callback registry (e.g. POSIX signals) Regardless of which type of interface is used, asynchronous functions by definition interact differently with their callers; there is class can match on more criteria than Application, or the Router interface can be subclassed for maximum customization. Router interface extends HTTPServerConnectionDelegate to provide additional routing0 码力 | 359 页 | 347.32 KB | 1 年前3Tornado 6.1 Documentation
Deferred) • Deliver to a queue • Callback registry (e.g. POSIX signals) Regardless of which type of interface is used, asynchronous functions by definition interact differently with their callers; there is class can match on more criteria than Application, or the Router interface can be subclassed for maximum customization. Router interface extends HTTPServerConnectionDelegate to provide additional routing ˓→path]) router = HTTPMethodRouter(Application()) server = HTTPServer(router) ReversibleRouter interface adds the ability to distinguish between the routes and reverse them to the original urls using route’s0 码力 | 245 页 | 904.24 KB | 1 年前3Tornado 6.0 Documentation
officially supported and is recommended only for development use. Without reworking Tornado IOLoop interface, it’s not possible to add a native Tornado Windows IOLoop implementation or leverage Windows’ IOCP Deferred) • Deliver to a queue • Callback registry (e.g. POSIX signals) Regardless of which type of interface is used, asynchronous functions by definition interact differently with their callers; there is class can match on more criteria than Application, or the Router interface can be subclassed for maximum customization. Router interface extends HTTPServerConnectionDelegate to provide additional routing0 码力 | 245 页 | 885.76 KB | 1 年前3Tornado 6.4 Documentation
Deferred) • Deliver to a queue • Callback registry (e.g. POSIX signals) Regardless of which type of interface is used, asynchronous functions by definition interact differently with their callers; there is class can match on more criteria than Application, or the Router interface can be subclassed for maximum customization. Router interface extends HTTPServerConnectionDelegate to provide additional routing path]) router = HTTPMethodRouter(Application()) server = HTTPServer(router) ReversibleRouter interface adds the ability to distinguish between the routes and reverse them to the original urls using route’s0 码力 | 268 页 | 1.09 MB | 1 年前3
共 424 条
- 1
- 2
- 3
- 4
- 5
- 6
- 43