Differences between revisions 1 and 4 (spanning 3 versions)
Revision 1 as of 2002-09-05 20:32:03
Size: 2867
Editor: 216
Comment: initial doc, by robin, author of Wasp
Revision 4 as of 2007-07-17 23:47:49
Size: 2561
Editor: 86-41-107-124
Comment: update for version 2.0
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
   URL:: http://www.execulink.com/~robin/wasp/readme.html
   version:: 1.33 September 5, 2002
   URL:: http://robinparmar.com/wasp.html
   version:: 2.00 (''[[Date(2007-07-17T00:00:00)]]'')
Line 8: Line 8:
   Python versions:: Python 2.2 and above    Python versions:: Python 2.5 and above
Line 12: Line 12:
Wasp works in two modes: client and server. In client mode Wasp requires no deployment platform. In server mode it works through CGI with Apache Server. Wasp works in three modes. In client mode Wasp requires no deployment platform but compiles templates in batch mode. In CGI mode it works with an appropriate web server. In server mode it runs embedded in its own threaded web server.
Line 16: Line 16:
Suitable in those cases where CGI gives reasonable performance, that is, all but the most popular of web applications. Suitable for those who wish the conventional URL/file website paradigm. Not (as) suitable if you wish to code your entire site in an OOP fashion with virtual files. Not WSGI compatible.
Line 20: Line 20:
The file inclusion, macro expansion, and other features may be used as-is. However, Wasp is designed primarily for those who wish to code in Python to create dynamic web sites. A streamlined CGI environment is provided with easy access to forms, cookies, a session mechanism, date module, table browser, etc. Python code may be freely added as plugins with no special dependencies or restrictions. Code may also be inserted into page templates. A streamlined web environment is provided with easy access to CGI info, cookies, sessions, etc.
Line 28: Line 28:
A robust database-independent server-side session mechanism is provided, which uses cookies to store unique keys. This can be used for Identification and Authentication as the designer wishes. A robust database-independent server-side session mechanism is provided, which uses cookies to store unique keys. This can be used for identification and authentication as the designer wishes.
Line 32: Line 32:
Wasp can be linked to any database with a Python interface, and contains a module to simplify the handling of tabular data such as that contained in a cursor. None provided, so you can use your favourite. Wasp is database agnostic.
Line 36: Line 36:
Wasp contains a simple templating system that encourages the separation of code and HTML. Python code is not allowed in template files, but template code is encouraged in Python files. Wasp contains a simple templating system that allows Python code in template files if you so wish.
Line 40: Line 40:
Wasp was developed when there were relatively few alternatives for Rapid Application Development in Python for the web. Now there are many templates and frameworks. Wasp distinguishes itself in its maturity (two years of active development), currency (still actively being improved), simplicity (installs as easy as any CGI handler), adherence to standard CGI model (no Zope here), ability to run in client mode (no web server required to get benefits of templating), remote debugging (really a life-saver), and thorough documentation. The inclusion of modules for tabular data and date handling rounds out the suite of tools. Wasp was developed when there were relatively few alternatives for Rapid Application Development in Python for the web. Now there are many such. Wasp distinguishes itself in its maturity (in development since 2001), currency (new version provides significant improvements), simplicity (installs easily with no dependencies), adherence to standard web paradigms (files are still files, URLs are still URLs), ability to run in command-line mode (no web server required to get the benefits of templating), remote debugging (really a life-saver), and thorough documentation.
Line 42: Line 42:
Wasp is not appropriate in cases where CGI itself is a limiting factor. However, the number of sites that really need to serve thousands of complex hits an hour are relatively few.

In the future, the example files will be expanded to include a full web site with sessions, cookies, etc. A module for connectivity with fastcgi is also proposed.
Wasp may not be appropriate for high-traffic sites. Here the CGI mode might be a limiting factor, and the embedded web server mode is not (as of yet) sufficiently tested under duress to recommend.
Line 50: Line 48:
Any Apache setup with Python 2.2 Any Apache setup with Python 2.5

Masthead

URL

http://robinparmar.com/wasp.html

version

2.00 (Date(2007-07-17T00:00:00))

licence
GPL
platforms
Linux, Windows
Python versions
Python 2.5 and above

Deployment Platforms

Wasp works in three modes. In client mode Wasp requires no deployment platform but compiles templates in batch mode. In CGI mode it works with an appropriate web server. In server mode it runs embedded in its own threaded web server.

Suitability

Suitable for those who wish the conventional URL/file website paradigm. Not (as) suitable if you wish to code your entire site in an OOP fashion with virtual files. Not WSGI compatible.

Development Interfaces

Python code may be freely added as plugins with no special dependencies or restrictions. Code may also be inserted into page templates. A streamlined web environment is provided with easy access to CGI info, cookies, sessions, etc.

Environment Access

Wasp can access any Python modules, stored in shared or restricted locations. There are no limitations on how the designer partitions business logic from other components.

Session, Identification and Authentication

A robust database-independent server-side session mechanism is provided, which uses cookies to store unique keys. This can be used for identification and authentication as the designer wishes.

Persistence Support

None provided, so you can use your favourite. Wasp is database agnostic.

Presentation Support

Wasp contains a simple templating system that allows Python code in template files if you so wish.

InTheirOwnWords

Wasp was developed when there were relatively few alternatives for Rapid Application Development in Python for the web. Now there are many such. Wasp distinguishes itself in its maturity (in development since 2001), currency (new version provides significant improvements), simplicity (installs easily with no dependencies), adherence to standard web paradigms (files are still files, URLs are still URLs), ability to run in command-line mode (no web server required to get the benefits of templating), remote debugging (really a life-saver), and thorough documentation.

Wasp may not be appropriate for high-traffic sites. Here the CGI mode might be a limiting factor, and the embedded web server mode is not (as of yet) sufficiently tested under duress to recommend.

Comments

Hosting

Any Apache setup with Python 2.5

Wasp (last edited 2008-11-15 13:59:52 by localhost)

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