The document discusses caching and synchronization of server data across multiple views and users in Flex applications. It proposes storing all fetched entities from the server in a single cache, binding views to the cache, and updating views when the server sends a notice that an entity has changed. When an entity is requested but not in the cache, a wrapper object is returned and the entity is queued to be fetched. The approach requires unique entity keys, abilities to get entities by key or keys, and support for versioned entities on the server-side.