On 15/07/13 16:10, Florian Apolloner wrote:
On Monday, July 15, 2013 4:14:43 PM UTC+2, Jannis Leidel wrote:
If you're suggesting to move the FastCGI code into a separate app: +1
I'd have just dropped it, but yes we can move it out; although someone
else will have to step up to continue maintaining it (if there is a need
to maintain it).
Florian
What about SCGI and AJP support? Is that going?
Seems silly to drop FastCGI which is probably the most popular of three
and leave the other two intact. If you're going to drop something drop
all three.
At least then it is clear to users that WSGI is the only supported
option in Django.
Third parties can then maintain FastCGI, SCGI and AJP support (which I
believe all come from flup anayway).
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
For more options, visit https://groups.google.com/groups/opt_out.
