450442 - Make the front page object invalidation capable

Status: RESOLVED FIXED

(addons.mozilla.org Graveyard :: Public Pages, defect)

Description

[Basil Hashem [:baz]]

Need to modify the AMO front page to use the object invalidation framework.

Comment 1

[Michael Morgan [:morgamic]]

This will cover utilizing the improved cache policy from bug 425315.

Comment 2

[Fred Wenzel [:wenzel]]

Attachment: Object-caching capable front page

This is the "full version" of attachment 337237 [details] [diff] [review]. The whole front page uses per-addon caching along with association-based add-on fetching, so we only haul around the data that's needed and can expire the cache on a per-addon basis.

Note that the add-on model's afterSave() callback is currently the only place where the cache expiration is triggered. That's probably not the only place where this needs to happen though -- in the versions model as well, maybe?

Comment 3

[Wil Clouser [:clouserw]]

Comment on attachment 338263 [details] [diff] [review]
Object-caching capable front page

It doesn't have syntax errors. :)  I didn't test all the aspects of it so we could land sooner and get more feedback time from everyone.

Comment 4

[Fred Wenzel [:wenzel]]

Checked in to r18252. I'll file another bug so we actually invalidate the add-on objects wherever necessary.

Comment 5

[Fred Wenzel [:wenzel]]

(In reply to comment #4)
> I'll file another bug so we actually invalidate the
> add-on objects wherever necessary.

Filed: bug 455385.