innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Edited faq.txt and fastcgi.txt changes from [4897] 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@4898 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2007-04-01 06:40:01 +00:00
parent 72dfcab0d4
commit 9b6a518e17
2 changed files with 13 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/faq.txt
View File

@ -328,9 +328,9 @@ Do I have to use mod_python?
Although we recommend mod_python for production use, you don't have to use it, Although we recommend mod_python for production use, you don't have to use it,
thanks to the fact that Django uses an arrangement called WSGI_. Django can thanks to the fact that Django uses an arrangement called WSGI_. Django can
talk to any WSGI-enabled server. Other common non-mod_python deployment talk to any WSGI-enabled server. Other non-mod_python deployment setups are
setups are FastCGI, SCGI, or AJP. See `How to use Django with FastCGI, SCGI or FastCGI, SCGI or AJP. See `How to use Django with FastCGI, SCGI or AJP`_ for
AJP`_ for full information. full information.
Also, see the `server arrangements wiki page`_ for other deployment strategies. Also, see the `server arrangements wiki page`_ for other deployment strategies.

17
docs/fastcgi.txt
View File

@ -4,13 +4,14 @@ How to use Django with FastCGI, SCGI or AJP
Although the `current preferred setup`_ for running Django is Apache_ with Although the `current preferred setup`_ for running Django is Apache_ with
`mod_python`_, many people use shared hosting, on which protocols such as `mod_python`_, many people use shared hosting, on which protocols such as
FastCGI, SCGI, or AJP are the only viable options. In some setups, these protocols FastCGI, SCGI or AJP are the only viable options. In some setups, these protocols
also allow better security -- and, possibly, better performance -- than mod_python. also allow better security -- and, possibly, better performance -- than mod_python.
.. admonition:: Note .. admonition:: Note
This document primarily talks about FastCGI, although other flup-supported This document primarily focuses on FastCGI. Other protocols, such as SCGI
protocols such as SCGI and AJP are supported. and AJP, are also supported, through the ``flup`` Python package. See the
"Protocols" section below for specifics about SCGI and AJP.
Essentially, FastCGI is an efficient way of letting an external application Essentially, FastCGI is an efficient way of letting an external application
serve pages to a Web server. The Web server delegates the incoming Web requests serve pages to a Web server. The Web server delegates the incoming Web requests
@ -86,10 +87,12 @@ or socket you specified when starting the FastCGI server.
Protocols Protocols
--------- ---------
Django supports all the protocols that flup_ does, namely fastcgi_, `SCGI`_, and `AJP1.3`_. Django supports all the protocols that flup_ does, namely fastcgi_, `SCGI`_ and `AJP1.3`_
Your preferred protocol can be selected by using the `protocol=`<protocol_name> option with (the Apache JServ Protocol, version 1.3). Select your preferred protocol by using the
`./manage.py runfcgi` where <protocol-name> may currently be one of: `fcgi` (the default), `protocol=`<protocol_name> option with `./manage.py runfcgi` -- where <protocol_name>
`scgi`, or `ajp`. may be one of: `fcgi` (the default), `scgi` or `ajp`. For example::
./manage.py runfcgi --protocol=scgi
.. _flup: http://www.saddi.com/software/flup/ .. _flup: http://www.saddi.com/software/flup/
.. _fastcgi: http://www.fastcgi.com/ .. _fastcgi: http://www.fastcgi.com/