clarencen/lshift — Issue #209: Content request caching
Author: clarencen
Created: 2011-11-14 22:42:06+00:00
State: open

The call to request an entity's content gets proxied through the agent without any caching at all. We could consider some kind of caching in the agent that has a configurable expiry. Calls to cached content would either be served from the cache or 304'ed where appropriate.

The expiry time might have to be chosen carefully. Potentially the main use case is to stop the end user clicking a lot in the UI and issuing heavy calls for each click.

The other option is to introduce caching at the participant, which would have less chance of going stale, since the participant has more knowledge of how long it can cache things for.

See also #258 for a ticket relating to the client side handling of this