Tornado 5.1 Documentation
While it is possible to use the Tornado web framework in a WSGI container (WSGIAdapter), or use the Tornado HTTP server as a container for other WSGI frameworks (WSGIContainer), each of these combinations deploying it is a little different from other Python web frameworks. Instead of configuring a WSGI container to find your application, you write a main() function that starts the server: def main(): app = WSGI and Google App Engine Tornado is normally intended to be run on its own, without a WSGI container. However, in some environments (such as Google App Engine), only WSGI is allowed and applications0 码力 | 243 页 | 895.80 KB | 1 年前3Tornado 5.1 Documentation
While it is possible to use the Tornado web framework in a WSGI container (WSGIAdapter), or use the Tornado HTTP server as a container for other WSGI frameworks (WSGIContainer), each of these combinations deploying it is a little different from other Python web frameworks. Instead of configuring a WSGI container to find your application, you write a main() function that starts the server: def main(): app WSGI and Google App Engine Tornado is normally intended to be run on its own, without a WSGI container. However, in some environments (such as Google App Engine), only WSGI is allowed and applications0 码力 | 359 页 | 347.32 KB | 1 年前3Tornado 4.5 Documentation
While it is possible to use the Tornado web framework in a WSGI container (WSGIAdapter), or use the Tornado HTTP server as a container for other WSGI frameworks (WSGIContainer), each of these combinations deploying it is a little different from other Python web frameworks. Instead of configuring a WSGI container to find your application, you write a main() function that starts the server: def main(): app WSGI and Google App Engine Tornado is normally intended to be run on its own, without a WSGI container. However, in some environments (such as Google App Engine), only WSGI is allowed and applications0 码力 | 333 页 | 322.34 KB | 1 年前3Tornado 4.5 Documentation
While it is possible to use the Tornado web framework in a WSGI container (WSGIAdapter), or use the Tornado HTTP server as a container for other WSGI frameworks (WSGIContainer), each of these combinations deploying it is a little different from other Python web frameworks. Instead of configuring a WSGI container to find your application, you write a main() function that starts the server: def main(): app = WSGI and Google App Engine Tornado is normally intended to be run on its own, without a WSGI container. However, in some environments (such as Google App Engine), only WSGI is allowed and applications0 码力 | 222 页 | 833.04 KB | 1 年前3Tornado 6.1 Documentation
offer a full-stack alternative to WSGI. While it is possible to use the Tornado HTTP server as a container for other WSGI frameworks (WSGIContainer), this combination has limitations and to take full advantage deploying it is a little different from other Python web frameworks. Instead of configuring a WSGI container to find your application, you write a main() function that starts the server: 34 Chapter 6. Documentation RequestHandler classes are designed for use with the Tornado HTTPServer and cannot be used in a generic WSGI container. class tornado.wsgi.WSGIContainer(wsgi_application: WSGIAppType) Makes a WSGI-compatible function0 码力 | 245 页 | 904.24 KB | 1 年前3Tornado 6.0 Documentation
offer a full-stack alternative to WSGI. While it is possible to use the Tornado HTTP server as a container for other WSGI frameworks (WSGIContainer), this combination has limitations and to take full advantage deploying it is a little different from other Python web frameworks. Instead of configuring a WSGI container to find your application, you write a main() function that starts the server: def main(): app = RequestHandler classes are designed for use with the Tornado HTTPServer and cannot be used in a generic WSGI container. class tornado.wsgi.WSGIContainer(wsgi_application: WSGIAppType) Makes a WSGI-compatible function0 码力 | 245 页 | 885.76 KB | 1 年前3Tornado 6.4 Documentation
offer a full-stack alternative to WSGI. While it is possible to use the Tornado HTTP server as a container for other WSGI frameworks (WSGIContainer), this combination has limitations and to take full advantage deploying it is a little different from other Python web frameworks. Instead of configuring a WSGI container to find your application, you write a main() function that starts the server: import asyncio async RequestHandler classes are designed for use with the Tornado HTTPServer and cannot be used in a generic WSGI container. class tornado.wsgi.WSGIContainer(wsgi_application: WSGIAppType, executor: Optional[Executor] =0 码力 | 268 页 | 1.09 MB | 1 年前3Tornado 6.2 Documentation
offer a full-stack alternative to WSGI. While it is possible to use the Tornado HTTP server as a container for other WSGI frameworks (WSGIContainer), this combination has limitations and to take full advantage deploying it is a little different from other Python web frameworks. Instead of configuring a WSGI container to find your application, you write a main() function that starts the server: import asyncio async RequestHandler classes are designed for use with the Tornado HTTPServer and cannot be used in a generic WSGI container. class tornado.wsgi.WSGIContainer(wsgi_application: WSGIAppType) Makes a WSGI-compatible function0 码力 | 260 页 | 1.06 MB | 1 年前3Tornado 6.4 Documentation
offer a full-stack alternative to WSGI. While it is possible to use the Tornado HTTP server as a container for other WSGI frameworks (WSGIContainer), this combination has limitations and to take full advantage deploying it is a little different from other Python web frameworks. Instead of configuring a WSGI container to find your application, you write a main() function that starts the server: import asyncio async RequestHandler classes are designed for use with the Tornado HTTPServer and cannot be used in a generic WSGI container. class tornado.wsgi.WSGIContainer(wsgi_application: WSGIAppType, executor: Optional[Executor] =0 码力 | 268 页 | 1.09 MB | 1 年前3Tornado 6.4 Documentation
offer a full-stack alternative to WSGI. While it is possible to use the Tornado HTTP server as a container for other WSGI frameworks (WSGIContainer), this combination has limitations and to take full advantage deploying it is a little different from other Python web frameworks. Instead of configuring a WSGI container to find your application, you write a main() function that starts the server: import asyncio async RequestHandler classes are designed for use with the Tornado HTTPServer and cannot be used in a generic WSGI container. class tornado.wsgi.WSGIContainer(wsgi_application: WSGIAppType, executor: Optional[Executor] =0 码力 | 268 页 | 1.09 MB | 1 年前3
共 20 条
- 1
- 2