⇤ ← Revision 1 as of 2003-02-08 19:56:20
1245
Comment:
|
2256
|
Deletions are marked like this. | Additions are marked like this. |
Line 13: | Line 13: |
Draco runs on as a mod_python application under Apache. Apache 1.3 is recommended, but Apache 2.0 should work too with the latest mod_python CVS version. | Draco plugs into the Apache/mod_python combination. Apache 1.3 is recommended, but Apache 2.0 should work too with the latest mod_python CVS version. |
Line 27: | Line 27: |
Draco make use of the namespace concept. A namespace is a place where you can store (almost) arbitrary Python variables using the Python dictionary API (ns['varname'] ect.). There are different namespaces, some of which are persistent. These include the ''session'', ''user'', ''application'' and ''server'' namespace. | Draco make use of the '''namespace''' concept. A namespace is a place where you can store (almost) arbitrary Python variables using the Python dictionary API (ns['varname'] etc.). There are different namespaces, some of which are persistent. These include the ''session'', ''user'', ''application'' and ''server'' namespace. Technically, persistentce is implemented by a relational database backend. |
Line 30: | Line 32: |
==== Process Logic versus Markup Logic ==== In Draco rogram logic is conceptually separated into process and markup logic. The process logic is the logic that processes a request and performs the desired action. The markup logic is the logic that formats the results of the process logic in the html. ==== Handlers and Templates ==== Draco makes use of '''handlers''' and '''templates'''. The process logic is put in a handler. This handler processes the client's request and performs the requested operations. The result of these operations is put in a special namespace called the ''interface''. The template is template as exist in many web frameworks, namely an html file with embedded code blocks. The only thing this code should do is format the results from the '''interface''' namespace into the html. All variables from the '''interface''' namespace are directly available to this code as global variables. |
A framework for WebProgramming.
Masthead
- URL
- version
0.9.2 (Date(2003-01-14T00:00:00))
- licence
- GPL
- platforms
- Developed for Unix/Apache with mod_python. Windows support untested.
- Python versions
- 2.2
Deployment Platforms
Draco plugs into the Apache/mod_python combination. Apache 1.3 is recommended, but Apache 2.0 should work too with the latest mod_python CVS version.
Suitability
Development Interfaces
Environment Access
Session, Identification and Authentication
Draco has an integrated session management mechanism. Sessions can be logged in and made persistent. Authentication has to be performed in the application.
Persistence Support
Draco make use of the namespace concept. A namespace is a place where you can store (almost) arbitrary Python variables using the Python dictionary API (ns['varname'] etc.). There are different namespaces, some of which are persistent. These include the session, user, application and server namespace.
Technically, persistentce is implemented by a relational database backend.
Presentation Support
Process Logic versus Markup Logic
In Draco rogram logic is conceptually separated into process and markup logic. The process logic is the logic that processes a request and performs the desired action. The markup logic is the logic that formats the results of the process logic in the html.
Handlers and Templates
Draco makes use of handlers and templates. The process logic is put in a handler. This handler processes the client's request and performs the requested operations. The result of these operations is put in a special namespace called the interface.
The template is template as exist in many web frameworks, namely an html file with embedded code blocks. The only thing this code should do is format the results from the interface namespace into the html. All variables from the interface namespace are directly available to this code as global variables.
InTheirOwnWords
Comments