Book Image

CherryPy Essentials: Rapid Python Web Application Development

By : Sylvain Hellegouarch
Book Image

CherryPy Essentials: Rapid Python Web Application Development

By: Sylvain Hellegouarch

Overview of this book

<p>CherryPy is a Python library for web development that allows developers to build web applications in the same way as any other object-oriented Python program. Enriched by several years of active development, it has become one of the most established toolkits for building solid and high-performance web applications in Python. CherryPy abstracts the complex low-level HTTP protocol into an easy-to-use interface that respects Python idioms. The library aims at being simple to learn for a beginner while offering the most advanced features to fluent Python developers. For these reasons CherryPy was chosen to be at the heart of the popular and feature-rich TurboGears web framework. CherryPy-powered web applications are stand-alone Python applications with their own embedded multi-threaded web server, but can also run behind Apache or IIS for scalability.</p>

Related Content you might be interested in

Current Title:

Small book image
CherryPy Essentials: Rapid Python Web Application Development
Sylvain Hellegouarch
Mar, 2007 | 272 pages
Small book image
Real-World Next.js
Michele Riva
Feb, 2022 | 366 pages
Small book image
Isomorphic JavaScript Web Development
Konstantin Tarkus | Tomas Alabes
Oct, 2017 | 226 pages
Small book image
Build Applications with Meteor
Dobrin Ganev
May, 2017 | 388 pages
Table of Contents (17 chapters)
CherryPy Essentials
CherryPy Essentials
Credits
Credits
About the Author
About the Author
Acknowledgement
Acknowledgement
About the Reviewers
About the Reviewers
Preface
Preface
Free Chapter
1
Introduction to CherryPy
Introduction to CherryPy
Overview
History of CherryPy
The Community
CherryPy Project Strengths
Beyond CherryPy
Through the Book
Summary
2
Download and Install CherryPy
Download and Install CherryPy
Requirements
Overview
Installation from a Tarball
Installation through Easy Install
Installation from Subversion
Testing your Installation
Keeping CherryPy Up to Date
Summary
3
Overview of CherryPy
Overview of CherryPy
Vocabulary
Basic Example
Built-In HTTP Server
Internal Engine
Configuration
Object Publisher Engine
Library
Tools
Error and Exception Handling
Summary
4
CherryPy in Depth
CherryPy in Depth
HTTP Compliance
Multiple HTTP Servers
Multi-Threaded Application Server
URI Dispatching
Hook into CherryPy's Core Engine
CherryPy Toolbox
Static Resource Serving
WSGI Support
Summary
5
A Photoblog Application
A Photoblog Application
A Photoblog Application
Photoblog Entities
Vocabulary
DBMSes Overview
Object-Relational Mapping
Photoblog Application Entity Modeling
Querying Units
Extending the Data Access Layer
Summary
6
Web Services
Web Services
Traditional Web Development
REST
Uniform Resource Identifier
HTTP Methods
Putting it Together
REST Interface through CherryPy
Atom Publishing Protocol
Atom XML-Document Format
APP Implementation
Summary
7
The Presentation Layer
The Presentation Layer
HTML
XML
XHTML
CSS
DHTML
Templating
Kid—The Templating Engine
Photoblog Design Preparation
Photoblog Design in Detail
Mochikit
Developing the Photoblog Design
Summary
8
Ajax
Ajax
Rise of the Rich-Client Applications
Ajax
JSON
Applying Ajax to our Application
Summary
9
Testing
Testing
Why Testing
Planning a Test
Common Testing Approach
Unit Testing
Unit Testing Web Applications
Performance and Load Testing
Functional Testing
Summary
10
Deployment
Deployment
Configuration
Deployment
SSL
Summary
Index
Index

Ajax

In the year 2005, Jesse James Garrett (http://www.adaptivepath.com/publications/essays/archives/000385.php) coined the term Ajax to designate a set of technology that he was about to present to one of his clients. It has since then left its original author's hands and is today the referenced term for what we introduced in the previous section about making web applications look more dynamic and interactive.

Ajax stands for Asynchronous JavaScript and XML, and covers a set of technologies applied to a web environment. Let's review each part of the acronym:

  • Asynchronous: In a client-server environment, there are two grand principles; either your operation is running synchronously to the rest of the program or not. If it is, then the program pauses until the operation terminates, and if it is not, then the operation returns immediately and lets the program continue. Once the operation is finished, it informs its main program through a callback function.

    In the context of a web application...

Previous Section
End of Section 3
Next Section