Closed Bug 989181 Opened 10 years ago Closed 8 years ago

Use CDN for app ratings responses


(Marketplace Graveyard :: Consumer Pages, defect, P3)



(Not tracked)



(Reporter: cvan, Unassigned)




(Keywords: perf, Whiteboard: [marketplace-transition])

As of bug 983815, we're using the CDN for API responses for the homepage, category, and search endpoints.

Because we lazy-load these in on the detail pages, and they take a few seconds on even fast wifi, let's use the CDN for the ratings endpoints too:

More of a consumer pages bug (I suspect most of the changes will have to be made in fireplace)
Component: API → Consumer Pages
No longer blocks: tarako-marketplace
Blocks: 992365
Priority: -- → P3
Assignee: nobody → mpillard
Like bug 991955 this is not trivial because user authentication is involved. I'm pretty sure we could rework some of that code to make sure we don't use user auth except when posting/editing, that would be a good start.
No longer blocks: 992365
Assignee: mpillard → nobody
Why is user authentication involved here?  Shouldn't the API response be the same no matter what and the choice to display a button or not be left up to the front end?
The API returns whether or not the user has already rated this app and whether or not he has already flagged each rating returned. The front-end then uses that info to figure out whether to display buttons or not.
Depends on: 1162061
See Also: → 1185614
Closed: 8 years ago
Resolution: --- → WONTFIX
Whiteboard: [marketplace-transition]
You need to log in before you can comment on or make changes to this bug.