If a good caching policy is in place, updating an aside isn't reflected. On update, asides should check each resources using the updated aside (via a class method ?) and refresh those resources' cache (think about multi-contexts & Revo < 2.1 - different cache system/methods).
If a good caching policy is in place, updating an aside isn't reflected. On update, asides should check each resources using the updated aside (via a class method ?) and refresh those resources' cache (think about multi-contexts & Revo < 2.1 - different cache system/methods).