wsgi — Interoperability with other Python frameworks and servers Running Tornado apps on WSGI servers Running WSGI apps on Tornado servers tornado.platform.asyncio — Bridge between asyncio and Tornado authentication. To authenticate with Twitter, register your application with Twitter at http://twitter.com/apps. Then copy your Consumer Key and Consumer Secret to the application settings twitter_consumer_key example, with this class you can mix Django and Tornado handlers in a single server. Running Tornado apps on WSGI servers class tornado.wsgi.WSGIAdapter(application) Converts a tornado.web.Application instance

wsgi — Interoperability with other Python frameworks and servers Running Tornado apps on WSGI servers Running WSGI apps on Tornado servers tornado.platform.caresresolver — Asynchronous DNS Resolver using authentication. To authenticate with Twitter, register your application with Twitter at http://twitter.com/apps. Then copy your Consumer Key and Consumer Secret to the application settings twitter_consumer_key example, with this class you can mix Django and Tornado handlers in a single server. Running Tornado apps on WSGI servers class tornado.wsgi.WSGIAdapter(application) Converts a tornado.web.Application instance

authentication. To authenticate with Twitter, register your application with Twitter at http://twitter.com/apps. Then copy your Consumer Key and Consumer Secret to the application settings twitter_consumer_key example, with this class you can mix Django and Tornado handlers in a single server. Running Tornado apps on WSGI servers class tornado.wsgi.WSGIAdapter(application) Converts a tornado.web.Application instance Deprecated since version 4.0: Use a regular Application and wrap it in WSGIAdapter instead. Running WSGI apps on Tornado servers class tornado.wsgi.WSGIContainer(wsgi_application) Makes a WSGI-compatible function

authentication. To authenticate with Twitter, register your application with Twitter at http://twitter.com/apps. Then copy your Consumer Key and Consumer Secret to the application settings twitter_consumer_key example, with this class you can mix Django and Tornado handlers in a single server. Running Tornado apps on WSGI servers class tornado.wsgi.WSGIAdapter(application) Converts a tornado.web.Application instance 6.0. 5.6. Integration with other services 135 Tornado Documentation, Release 5.1.1 Running WSGI apps on Tornado servers class tornado.wsgi.WSGIContainer(wsgi_application) Makes a WSGI-compatible function

authentication. To authenticate with Twitter, register your application with Twitter at http://twitter.com/apps. Then copy your Consumer Key and Consumer Secret to the application settings twitter_consumer_key server and I/O loop. The tornado.web.FallbackHandler class is often useful for mixing Tornado and WSGI apps in the same server. See https://github.com/bdarnell/django-tornado- demo for a complete example. log_exception can be overridden to customize the logging behavior when an exception is uncaught. Most apps that currently override _handle_request_exception can now use a combination of RequestHandler.log_exception

authentication. To authenticate with Twitter, register your application with Twitter at http://twitter.com/apps. Then copy your Consumer Key and Consumer Secret to the application settings twitter_consumer_key server and I/O loop. The tornado.web.FallbackHandler class is often useful for mixing Tornado and WSGI apps in the same server. See https://github.com/bdarnell/django-tornado- demo for a complete example. log_exception can be overridden to customize the logging behavior when an exception is uncaught. Most apps that currently override _handle_request_exception can now use a combination of RequestHandler.log_exception

authentication. To authenticate with Twitter, register your application with Twitter at http://twitter.com/apps. Then copy your Consumer Key and Consumer Secret to the application settings twitter_consumer_key server and I/O loop. The tornado.web.FallbackHandler class is often useful for mixing Tornado and WSGI apps in the same server. See https://github.com/bdarnell/django-tornado-demo for a complete example. static log_exception can be overridden to customize the logging behavior when an exception is uncaught. Most apps that currently override _handle_request_exception can now use a combination of RequestHandler.log_exception

authentication. To authenticate with Twitter, register your application with Twitter at http://twitter.com/apps. Then copy your Consumer Key and Consumer Secret to the application settings twitter_consumer_key server and I/O loop. The tornado.web.FallbackHandler class is often useful for mixing Tornado and WSGI apps in the same server. See https://github.com/bdarnell/django-tornado-demo for a complete example. static log_exception can be overridden to customize the logging behavior when an exception is uncaught. Most apps that currently override _handle_request_exception can now use a combination of RequestHandler.log_exception

authentication. To authenticate with Twitter, register your application with Twitter at http://twitter.com/apps. Then copy your Consumer Key and Consumer Secret to the application settings twitter_consumer_key Documentation, Release 6.2 The tornado.web.FallbackHandler class is often useful for mixing Tornado and WSGI apps in the same server. See https://github.com/bdarnell/django-tornado-demo for a complete example. static log_exception can be overridden to customize the logging behavior when an exception is uncaught. Most apps that currently override _handle_request_exception can now use a combination of RequestHandler.log_exception

authentication. To authenticate with Twitter, register your application with Twitter at http://twitter.com/apps. Then copy your Consumer Key and Consumer Secret to the application settings twitter_consumer_key server and I/O loop. The tornado.web.FallbackHandler class is often useful for mixing Tornado and WSGI apps in the same server. See https://github.com/bdarnell/django-tornado- demo for a complete example. log_exception can be overridden to customize the logging behavior when an exception is uncaught. Most apps that currently override _handle_request_exception can now use a combination of RequestHandler.log_exception