-The WSGI handler in this module examines the SCRIPT_FILENAME variable
-of the requests it handles -- that is, the physical file corresponding
-to the request, as determined by the webserver -- determining what to
-do with the request based on the extension of that file.
-
-By default, it handles files named `.wsgi' by compiling them into
-Python modules and using them, in turn, as chained WSGI handlers, but
-handlers for other extensions can be installed as well.
-
-When handling `.wsgi' files, the compiled modules are cached and
-reused until the file is modified, in which case the previous module
-is discarded and the new file contents are loaded into a new module in
-its place. When chaining such modules, an object named `wmain' is
-first looked for and called with no arguments if found. The object it
-returns is then used as the WSGI application object for that module,
-which is reused until the module is reloaded. If `wmain' is not found,
-an object named `application' is looked for instead. If found, it is
-used directly as the WSGI application object.
+The WSGI handler in this module ensures that the SCRIPT_FILENAME
+variable is properly set in every request and points out a file that
+exists and is readable. It then dispatches the request in one of two
+ways: If the header X-Ash-Python-Handler is set in the request, its
+value is used as the name of a handler object to dispatch the request
+to; otherwise, the file extension of the SCRIPT_FILENAME is used to
+determine the handler object.
+
+The name of a handler object is specified as a string, which is split
+along its last constituent dot. The part left of the dot is the name
+of a module, which is imported; and the part right of the dot is the
+name of an object in that module, which should be a callable adhering
+to the WSGI specification. Alternatively, the module part may be
+omitted (such that the name is a string with no dots), in which case
+the handler object is looked up from this module.
+
+By default, this module will handle files with the extensions `.wsgi'
+or `.wsgi2' using the `chain' handler, which chainloads such files and
+runs them as independent WSGI applications. See its documentation for
+details.