Composite versioning/timestamp

[jonkri]

The possibility for a client to know whether a sync is needed. Perhaps a version/date field on the composite endpoint.

Pros: We don't need to reload unless necessary.

Cons: It's state. :)

Since we can reload cheaply from a bandwidth perspective (we will be on WiFi), it's probably only a problem to reload if it could cause problems in the app. For instance, the process of redrawing everything or making sure things are consistent is complex.

[jonkri]

@hesa: What do you think?

[jonkri]

I would like to suggest that we make this optional for 1.0, unless we have "client-side" reasons to think that it should be in 1.0.