Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #28477 > unrolled thread

[web] Long-running process: FCGI? SCGI? WSGI?

Back to article view | Back to comp.lang.python

Contents

  [web] Long-running process: FCGI? SCGI? WSGI? Gilles <nospam@nospam.com> - 2012-09-05 14:03 +0200
    Re: [web] Long-running process: FCGI? SCGI? WSGI? Dieter Maurer <dieter@handshake.de> - 2012-09-06 08:07 +0200

#28477 — [web] Long-running process: FCGI? SCGI? WSGI?

Hello

To write a long-running web application, I'd like to some feedback
about which option to choose.

Apparently, the choice boilds down to this:
- FastCGI
- SCGI
- WSGI

It seems like FCGI and SCGI are language-neutral, while WSGI is
Python-specific.

Besides that, how to make an informed choice about which option to
choose?

Thank you.

[toc] | [next] | [standalone]

#28551

Gilles <nospam@nospam.com> writes:

> To write a long-running web application, I'd like to some feedback
> about which option to choose.
>
> Apparently, the choice boilds down to this:
> - FastCGI
> - SCGI
> - WSGI
>
> It seems like FCGI and SCGI are language-neutral, while WSGI is
> Python-specific.
>
> Besides that, how to make an informed choice about which option to
> choose?

Obviously, this depends on your environment. Some hosters, web servers,
applications may directly support one interface and not others.

If you control your whole environment, I would look for a newer
approach. I do not know "SCGI" but I know that "WSGI" is fairly recent.
This means that during its design, "FastCGI" was already known and
not deemed to be sufficient. Thus, you can expect more features
(more modularisation, in this case) in "WSGI".

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web