When a user updates a Trello object, we currently expire all of the data for that object. So the next get on the object will result in a server hit, irregardless of whether that data was dirty or not.
There are two ways we can solve this. One is we can let the user decide whether to expire the data or we can detect which data is dirty and mark it dirty ourselves. The latter strategy seems difficult, if not impossible, since Trello doesn't tell us what has changed.
When a user updates a Trello object, we currently expire all of the data for that object. So the next get on the object will result in a server hit, irregardless of whether that data was dirty or not.
There are two ways we can solve this. One is we can let the user decide whether to expire the data or we can detect which data is dirty and mark it dirty ourselves. The latter strategy seems difficult, if not impossible, since Trello doesn't tell us what has changed.