1.1 Overview

httpy's job is to get HTTP requests off the wire into your Python program, and to get HTTP responses from your program back onto the wire. Within this narrow ambit, we include batteries: you shouldn't have to resort to another library for anything between the wire and your app. At the same time, we aim for a sane and satisfying API. Beyond the basic modeling of HTTP Request and Response messages, httpy is organized around just two types of Python objects:

responders: A responder is a module or class with a respond() callable, which takes an httpy.Request object and returns an httpy.Response object.
couplers: A coupler takes a responder and puts it on the network.

The whole thing is rather boring: httpy's Request and Response objects are wooden representations of their HTTP counterparts. Likewise, couplers are just socket and gateway grunt work. About the only interesting twist is that Response objects represent both success and error responses: a responder may also raise a Response. The real interest, of course, is in your responders.