Changeset 748
- Timestamp:
- 10/21/05 13:46:27
- Files:
-
- trunk/docs/book/xml/apireference.xml (modified) (2 diffs)
- trunk/docs/book/xml/gettingstarted.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
trunk/docs/book/xml/apireference.xml
r713 r748 9 9 <section id="cherrypyrequest"> 10 10 <title>cherrypy.request</title> 11 <para>The cherrypy.request object contains request-related objects. Pretty lame description, 12 but that's all it does; it's a big data dump. At the beginning of each HTTP request, the 13 existing request object is destroyed, and a new one is created, (one request object for each 14 thread). Therefore, CherryPy (and you yourself) can stick data into cherrypy.request and not 15 worry about it conflicting with other requests.</para> 11 16 <section> 12 17 <title>cherrypy.request.remoteAddr</title> … … 131 136 <section id="cherrypyresponse"> 132 137 <title>cherrypy.response</title> 138 <para>The cherrypy.response object contains response-related objects. Pretty lame 139 description, but that's all it does; it's a big data dump. At the beginning of each HTTP 140 request, the existing response object is destroyed, and a new one is created, (one response 141 object for each thread). Therefore, CherryPy (and you yourself) can stick data into 142 cherrypy.response and not worry about it conflicting with other requests.</para> 133 143 <section> 134 144 <title>cherrypy.response.headerMap</title> trunk/docs/book/xml/gettingstarted.xml
r713 r748 81 81 </cmdsynopsis> 82 82 <para>Alternately, since CherryPy has no dependencies, you don't have to run setup.py. 83 Simply checkout the code into a directory which is on your Python path, such as your 84 site-packages directory. 85 </para> 83 Instead, checkout <code>/trunk/cherrypy</code> into a directory which is on your Python 84 path, such as <code>site-packages/cherrypy</code>.</para> 86 85 </section> 87 86 </section>

