Last Comment Bug 870557 - Move privacy policy out of app object in API
: Move privacy policy out of app object in API
Product: Marketplace
Classification: Server Software
Component: API (show other bugs)
: 1.0
: x86 Mac OS X
P4 normal (vote)
: 2013-05-23
Assigned To: Allen Short [:ashort]
Depends on:
Blocks: 869715 875012
  Show dependency treegraph
Reported: 2013-05-09 14:58 PDT by Matt Basta [:basta]
Modified: 2013-05-22 17:51 PDT (History)
3 users (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Matt Basta [:basta] 2013-05-09 14:58:30 PDT
The privacy policy of apps (especially for games) is almost three times as large as the whole rest of the app object for apps that have a privacy policy. The "Paddle Game" app has a privacy policy that's almost 20kb. Most seem to be around 5kb. For a field that less than a fraction of a percent of users will ever need to access, this takes up an inordinate amount of bandwidth. It also probably contributes to the slowness of the API because it requires an additional DB join to allow it to be localized.
Comment 1 User image Rob Hudson [:robhudson] 2013-05-17 13:28:31 PDT
+1. When the new search API comes aboard it would also mean we have to store this in elasticsearch (in each locale) to avoid a database hit, which could bloat our index.
Comment 2 User image Rob Hudson [:robhudson] 2013-05-22 09:33:16 PDT
I propose:

Which returns something like:
{"body": "..."}

On the backend it's just a simple query by id or slug, localized, and returned.
Comment 3 User image Matt Basta [:basta] 2013-05-22 09:47:05 PDT
I love it, ship it
Comment 4 User image Andy McKay [:andym] 2013-05-22 10:24:53 PDT
Please don't use _ in URLs, so far all our API URLs are one word, or if you must, use a -.

Note You need to log in before you can comment on or make changes to this bug.