MetricsDataPing: Difference between revisions

MetricsDataPing (view source)

221 bytes removed , 3 February 2012

→‎Server-side: Updated the description of the server's response to a new submission

Confirmed users

36

edits

@@ Line 310: / Line 310: @@
 *The server will store the JSON document into a daily staging collection with all other documents received during that date, UTC.
 *If the POST request contains a header with the ID of a previously submitted document, the server will delete that old document as part of the transaction of storing the new one.
-*The server will return an HTTP response to the client indicating success of the storage and a document ID. For the initial feature release, this ID will be the same as the one passed in (i.e. an installation GUID). It can easily be changed to be new each time (i.e. a document GUID). If the ID is new, the client should store it to be returned on the next submission.
+*The server will return an HTTP response to the client indicating success of both the deletion of the old document and storage of the new document.
 *In the future this response might also include instructions to the client for things such as changing timing or MetricsDataPing configuration.
 *Longitudinal data for 6 months (e.g. intensity of use) is stored cumulatively in the JSON objects indexed by document ID. ''Documents older than 6 months are deleted.''