Ticket #740 (closed enhancement: fixed)

Opened 11 months ago

Last modified 7 months ago

support caching of page results

Reported by: jsuttor Assigned to: pradeep
Priority: high Milestone: 0.9.0
Component: ambra Version: 0.8.2-SNAPSHOT
Keywords: cache Cc:
Blocking: Blocked By:

Description

there are two issues that prevent caching of page results:

  • page may be customized with user information, see #739
  • key for page result is URI + params (slightly different requests for the same article could generate many keys)

SimplePageCachingFilter should be overriden to:

  • not cache customized results
  • generate normalized keys, e.g. override 
    SimplePageCachingFilter.calculateKey(javax.servlet.http.HttpServletRequest)

Dependency Graph

Change History

01/07/08 17:08:10 changed by rich

  • milestone deleted.

02/29/08 09:49:17 changed by russ

  • milestone set to pubApp_0.8.2.2.

03/19/08 17:24:29 changed by jsuttor

  • status changed from new to assigned.

03/20/08 10:58:07 changed by jsuttor

  • milestone changed from pubApp_0.8.2.2 to pubApp_0.8.2.3.

03/20/08 12:36:17 changed by jsuttor

  • milestone changed from pubApp_0.8.2.3 to pubApp_0.8.2.2.

03/25/08 13:47:53 changed by rich

  • milestone deleted.

05/07/08 10:10:15 changed by pradeep

  • owner changed from jsuttor to pradeep.
  • status changed from assigned to new.
  • blocking changed.
  • blockedby changed.
  • milestone set to 0.9.0.

05/07/08 10:19:09 changed by pradeep

  • status changed from new to closed.
  • resolution set to fixed.

(In [5657]) Remove SimplePageCachingFilter? and its associated cache.

The object-cache now holds the blobs that this filter was caching. Moreover the object-cache is journal context aware and will be invalidated when article is deleted/re-ingested as well as when the journal membership changes.

This closes #740,#278 and addresses #610,#901.