Confirmed users
210
edits
Websites/Plugincheck/Plugin Status Service: Difference between revisions
Websites/Plugincheck/Plugin Status Service (view source)
Revision as of 08:25, 13 April 2014
, 13 April 2014→Database
Espressive (talk | contribs) mNo edit summary |
Espressive (talk | contribs) m (→Database) |
||
| Line 60: | Line 60: | ||
== Database == | == Database == | ||
As most all processing of the data happens on the client, the requirements from a database perspective are pretty low and only a few requirements are really needed to satisfy this dependency. | |||
# The database should support the ability to import, export and query JSON. Querying directly against JSON is not a requirement as long as the first two are well supported. | # The database should support the ability to import, export and query JSON. Querying directly against JSON is not a requirement as long as the first two are well supported. | ||
# Each plugin will be a self contained JSON document and updating the database from these JSON documents should be supported. | # Each plugin will be a self contained JSON document and updating the database from these JSON documents should be supported. See [https://github.com/ossreleasefeed/plugin-status-service/blob/master/data/adobe-flash-player.json Flash player JSON] for an example. | ||
# Queries against the data will be limited to 2 or 3 predefined queries. | # Queries against the data will be limited to 2 or 3 predefined queries. | ||
* The most used query will be to get all plugins for a specific operating system | * The most used query will be to get all plugins for a specific operating system | ||
* Query to extract all the data from | * Query to extract all the data from the database, will be run periodically. (~once in a fortnight) | ||
* Query to update data based on a JSON document as described in point 2 above. | * Query to update data based on a JSON document as described in point 2 above. | ||
== Development Depencies == | == Development Depencies == | ||