Differences between revisions 15 and 16
Revision 15 as of 2003-12-06 17:13:03
Size: 2657
Editor: tk-proxy
Revision 16 as of 2005-02-23 21:56:03
Size: 2657
Editor: dyn-71-21
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
   version:: 1.3.12 (''[[Date(2003-11-20T00:00:00)]]'')    version:: 1.3.12 (''[[Date(2005-02-23T00:00:00)]]'')

A framework for WebProgramming.





1.3.12 (Date(2005-02-23T00:00:00))


OSI approved licence - open source. (See http://spyce.sourceforge.net/download.html.)

Spyce should work on most platforms.
Python versions

Deployment Platforms

  • Integrated with Apache using mod_python or with any Web server using CGI.
  • With CGI, the lifespan of a program is determined by the Web server, but mod_python should provide long-lived processes.


The deployment of applications using CGI is usually permitted in all but the most restrictive hosting environments. The use of mod_python may be more appropriate to in-house deployments or more comprehensive hosting environments.

Development Interfaces

  • Python code inside HTML documents - comparable to ASP, JSP and PHP.
  • Spyce modules can be written in Python to provide extra functionality.

Environment Access

  • Access to resources is primarily done using the Python module system and other general environment access techniques.

Session, Identification and Authentication

  • Support for sessions which identify users is included, currently only with filesystem support for stored session information, although SQL-based storage seems to be planned.
  • No explicit authentication support seems to be included.

Persistence Support

  • Apart from session information, no persistence mechanisms are included.

Presentation Support

  • The embedded Python code concept gives a certain flexibility in presentation.
  • The Cheetah templating system is explicitly supported through a Spyce module.

Other presentation systems could presumably be used instead, given the ability to use other Python modules in the framework.



Spyce addresses many areas of interest to Web application developers within a widely-known *SP paradigm: sessions, pooled objects, templating, and so on. Some novel features are also supported: automatons, for example, which attempt to encapsulate multi-stage transactions (or "application flows" as the documentation calls them). However, by design, Spyce does not attempt to provide everything - it aims to do dynamic Web content generation well and integrate with other things easily (see http://spyce.sourceforge.net/wishlist.html). Moreover, it can also be used as a standalone processing tool completely outside a Web application environment. -- PaulBoddie

Spyce (last edited 2014-05-05 12:40:49 by DaleAthanasias)

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