01. Why another web library?

Basic principles:

• configuration in code, not in XML
• multiple web containers support
• extensible with injection points
• uniform client and server API
• bindings in annotations, DSL or any other convention you want
• fast startup times
• no static state
• easily testable
• decoupled from the rendering library
• toString() on HTTP request and response returns on the wire representation of the message
• no HTTP session
• embraces the Web and doesn't hide the details of HTTP (Etag, cache control, correct usage of status codes and HTTP methods etc.)