diff options
author | Lawouach <sh@defuze.org> | 2014-05-07 08:09:16 +0200 |
---|---|---|
committer | Lawouach <sh@defuze.org> | 2014-05-07 08:09:16 +0200 |
commit | d1a05aefd0959f464cbfc79ff613c4d09a02b571 (patch) | |
tree | fec1fd88ea51d4e4ddd4523f3b970edbd863bc50 | |
parent | e91a3d3d71709c2f5c585d9a5f68738a217a7b9f (diff) | |
download | cherrypy-d1a05aefd0959f464cbfc79ff613c4d09a02b571.tar.gz |
a little more info
-rw-r--r-- | sphinx/source/deploy.rst | 14 |
1 files changed, 12 insertions, 2 deletions
diff --git a/sphinx/source/deploy.rst b/sphinx/source/deploy.rst index 56d1dded..da0bc0e3 100644 --- a/sphinx/source/deploy.rst +++ b/sphinx/source/deploy.rst @@ -161,19 +161,29 @@ you may wish to integrate your CherryPy application within a different framework. To do so, we will benefit from the WSGI interface defined in :pep:`333` and :pep:`3333`. -Note that you should follow the basic rules when embedding CherryPy +Note that you should follow some basic rules when embedding CherryPy in a third-party WSGI server: - If you rely on the `"main"` channel to be published on, as it would happen within the CherryPy's mainloop, you should find a way to publish to it within the other framework's mainloop. -- Start the CherryPy's engine. +- Start the CherryPy's engine. This will publish to the `"start"` channel + of the bus. .. code-block:: python cherrypy.engine.start() +- Stop the CherryPy's engine when you terminate. This will publish + to the `"stop"` channel of the bus. + + .. code-block:: python + + cherrypy.engine.stop() + +- Do not call ``cherrypy.engine.block()``. + - Disable the built-in HTTP server since it will not be used. .. code-block:: python |