Infrastructure » Java Client

From discussion in maintenance standup today (Nov 10, 2014):

In the V1 architecture, LocalCache implementation for data objects and metadata objects worked well because because objects were immutable. However, in v2, we can't make that assumption for consumers, because the identifier passed in could be a series ID. There is not an external requirement to implement caching, and how it might be done in the context of both large and small objects seems to go beyond what could be handled through JCS configuration. Consensus was that context caching was an application consideration and that transparent caching could lead to inefficiencies such as double-caching, or unexpectedly and silently getting stale content.

The consensus is to remove it from get and getSysmeta, and redesign so that such the local cache is tied to the session.