HTTP is a stateless protocol. Any application state that exists in a request is encoded in one of the following places:
httpy doesn't pretend to know the best way for you to encode state in
your app's requests, nor the best way to object-represent this state. Instead,
it gives you the raw HTTP message, and a very minimal secondary API. There are a
few tools in httpy.utils that might be helpful - parse_body,
parse_cookie, parse_query - but you are free to translate
the Request to your application's object model however you like.