Problem/Motivation
In order to effect timely and useful caching and cache busting, we need to know that last time an entity was updated. Given a consistent means to check updated time we can know, for instance, when assets have gone stale in a client-side application.
This one small and consistent piece of information will allow us to build robust caching graphs across dependent entities and invalid their caches more timely and precisely.
Proposed resolution
Add the updated time to a field on the base entity class.
Remaining tasks
Add the field to a base entity class.
User interface changes
None.
API changes
None.
Related Issues
#2044579: [meta] Supporting single page application development on Drupal Core.