ideas

[buhman]

• add API and development documentation
• distributed proxy
• add pastebin (and design slightly more complex pastebin API spec, because these are actions instead of CRUD)
• rename
• (async) API client
• make tests suck less

api features:

• finish naive crud methods
• add "link" method and link resolving (requires model changes)
• implement expiry
• add response classes (json and …yaml?)
• add client error responses

I am uncertain if I should split logical components into separate services, or just add more routes/sub-applications. I like the idea of a homogeneous deployment, but I'm uncertain about the performance implications.

I am also uncertain of whether I want to make some "request translation middleware" for the legacy API--it's a little too flexible, and supporting all of that will suck.