this is a german Web-Mirror of PYTHON.ORG powered by Domainunion AG

Differences between revisions 68 and 69
Revision 68 as of 2003-02-11 05:23:46
Size: 4779
Editor: lsanca1-ar23-4-63-034-002
Comment:
Revision 69 as of 2003-02-11 05:33:04
Size: 5104
Editor: lsanca1-ar23-4-63-034-002
Comment:
Deletions are marked like this. Additions are marked like this.
Line 82: Line 82:
== Application Frameworks == == Python-based ==

=
== Application Frameworks ===
Line 92: Line 94:

== Servlet-like Engines ==
=== Servlet-like Engines ===
Line 101: Line 102:
== Variable Insertion-Replacement Templating Applications == === Variable Insertion-Replacement Templating Applications (Pre-processors) ===
Line 104: Line 105:
    * [https://archive.dstc.edu.au/aspy/ ASPy]
Line 105: Line 107:
    * ClearSilver
Line 113: Line 114:
    * [https://www.ccraig.org/software/pyhp/ PyHP]
Line 114: Line 116:
      [https://www.embl-heidelberg.de/~chenna/pythonpages/template.html Ramu's Python pages]     * [https://www.embl-heidelberg.de/~chenna/pythonpages/template.html Ramu's Python pages]
Line 117: Line 119:
    * [https://www.execulink.com/~robin1/wasp/readme.html WASP]
Line 120: Line 123:
== Embedding Python Interpreter into HTTP (Web) Servers == === Embedding the Python Interpreter into HTTP (Web) Servers ===
Line 124: Line 127:

== Python accessible ==

=== Variable Insertion-Replacement Templating Applications (Pre-processors) ===

    * ClearSilver

This topic guide is a word by word copy of PaulBoddie's [https://www.boddie.org.uk/python/web_frameworks.html Python Web Frameworks Overview]. Putting it into Wiki format hopefully allows more people to contribute.

The main purpose of this topic guide is to help in choosing between the plethora of frameworks and templating systems for web programming, without having to learn each of them. In addition, information about different PresentationTechnologies is also provided, where appropriate, since this can be a major deciding factor in choosing a framework.

Opinions based on experience are welcome, but framework or templating system authors should sign their comments with InTheirOwnWords to admit to a certain bias.

The rather strict format of the main entries (described in WebProgrammingTemplateHelp) should not been seen as a limit. Feel free to add new pages containing examples, direct comparisons etc.

When adding new entries choose WebProgrammingTemplate when creating the page.

There is an ALTERNATIVE classification of technologies below the one that follows immediately. The alternative classification section is up-to-date as of 2003-02-11

Multi Protocol Server

HTTP Server and CGI

Content Management Frameworks

Templating Systems

Web services

To Do

  • The templating systems should really get a different page layout, showing examples etc.
  • describe PHP and Java in the same format as quite a few will want to compare to them anyway
  • Is there any interest in a WebProgrammingShootOut?

Editor: DanielDittmar (this means only that I will adapt the entries to changes in the WebProgrammingTemplate and that I will try to keep the version entries current)

Alternative Classification

Python-based

Application Frameworks

Servlet-like Engines

Variable Insertion-Replacement Templating Applications (Pre-processors)

Embedding the Python Interpreter into HTTP (Web) Servers

Python accessible

Variable Insertion-Replacement Templating Applications (Pre-processors)

WebProgramming (last edited 2008-11-15 13:59:44 by localhost)

Unable to edit the page? See the FrontPage for instructions.