random unordered tasks

[hairmare]

We should move these into GRVs.

• find and implement standardized ways to offer sync capabilities to an offline client
• implement a standardized way for clients to store schemaless data
  • check if a simple key/value store won't fullfill most needs (ie. /core/app/hello/settings/<key>)
  • define a sensible base line for all remaining edge cases (ie. no proprietary blobs in the key/value store and options)
• update documentation with client recommendation for all major platforms (browsers, ios, ...)
• find a way to do i18n right while still allowing an offline client to switch languages
• implement api versions with some semver magic (parse the X-Version header and act accordingly, allow both sides of the comms to specify a version constraint and define behaivour when said constraint is violated)
• implement delayed storing of records (202 Accepted for when backends go missing)
• find a way to store multiple linked documents in an offline client and still allow $ref linking them.
• implement PATCH verb

[hairmare]

Almost all of the stuf for i18n has been landed on develop. I still need to find a way for the frontend to find out which strings are translatable and also a way mark this up in the json schemas properly.

[hairmare]

http://syncable.org/ might have ideas for our sync requirement... I still need to investigate.

[hairmare]

This is so old Imma just close it.