Aspen

Aspen relies on WSGI and Simplates.

The term "Simplates", premiered first by the Aspen team is meant to describe a file format the Aspen system uses to represent HTTP resources in general.

A Simplate is basically a single file containing one or more pages.

An entire website can be coded in one Simplate, making it very easy to serve in one response, instead the classic way most servers do it by allocating hundreds of thousand of responses to serve one meager website.

Because of this Aspen is extremely fast.

Make sure to read the documentation first. Simplates aren't that simple without the time spent reading about them.

Features:

• Aspen can be configured via an aspen.conf file
• Aspen configuration files look for Python objects based on this notation
• Aspen supports both blocking and non-blocking concurrency models
• Requests management
• Responses management
• Use Aspen from the console
• Alter program execution on server startup and shutdown
• Alter program execution on inbound and outbound HTTP requests/responses
• Aspen uses Tornado templates
• Aspen can be configured to shutdown when important files are changed
• Aspen translates URL paths like /wawa/foo.html to filesystem paths like ./%name/foo.html