Differences between revisions 110 and 111
⇤ ← Revision 110 as of 2004-03-12 05:48:50 →
Size: 7814
Editor: MikeRovner
Comment: wiki-link
← Revision 111 as of 2004-03-15 03:08:05 → ⇥
Size: 8001
Editor: c-180-204-7
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

'''or, more aptly put, Web ''Server'' Programming'''

''(Client-side programming is hardly covered anywhere in this wiki so far :-(, see remark towards the bottom of this page)''

or, more aptly put, Web Server Programming

(Client-side programming is hardly covered anywhere in this wiki so far :-(, see remark towards the bottom of this page)

This topic guide started out as a word by word copy of PaulBoddie's [http://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

The Web Framework Shootout (at http://colorstudy.com/docs/shootout.html) also covers several of these frameworks.

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

Web-based XML processing Engines

  • ["4Suite"]

HTML Shorthand Processors

I don't know what to really call these things. They're not templating systems. They're not variable substitution systems. They are something different.

What? I do not know. I will call them, "HTML Shorthand Processors." -- LionKimbro

Python-accessible

Servlet-like Engines

Variable Insertion-Replacement Templating Applications (Pre-processors)

Currently Hardly Considered

Python-based Web Client Programming

There is probably a huge amount of good stuff available from the people who are working actively with XML-RPC, Biztalk and other approaches to web services. More too from XML writes like [http://uche.ogbuji.net/uche.ogbuji.net/ Uche Ogbuji], who has put much good stuff on IBM's developerworks site, among other things.

Sadly nobody has categorised or classified it in the Wiki, so at the moment we have to scratch around.

Object Persistence and Object Relational Layers

See DatabaseProgramming for some guidance on available DatabaseInterfaces and related tools.

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

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