Things we need to look at/change:
- registration - needs revamp, proposal is to do it in content with microformat-like tagging of fields plus something to tell the browser whether it was successful or not post-submit.
- password changes in content - also need metadata in content.
- we're storing AMCDs in a SQLite DB in our implementation (separate from the standard HTTP cache). This might turn out to be common, in which case it might make sense to put some caching hints into our protocol (or not?) - something to think about.