Resets the mwLastWriteTime cookie to the current time.
Freebase.com uses the mwLastWriteTime cookie to optimize query responses; it guarantees that any responses will be at least as new as the mwLastWriteTime cookie. This cookie is normally updated by any write action, so a single application or single browser will generally see the results of its own writes with no additional effort.
However, the default mechanism does not ensure that one application will be able to see the results of writes by another application. The /api/service/touch request provides a way for an application to manually update its read horizon so it can see changes made by another application.
Note that an updated mwLastWriteTime cookie will make responses slower, since Freebase.com will not be able to use cached responses to satisfy queries, so you should generally not use this service unless you have a pressing need for one application to see up-to-date information being written by another application.
| Name | | touch |
| Description | | Resets the mwLastWriteTime cookie to current time. This ensures that any requests from the time you use this service gets you the latest data instead of possibly stale cached data. |
| Accessible Via | | /api/service/touch |
| HTTP GET | | True |
| HTTP POST | | True |
| Special Headers | | None |
| Login Required | | False |
| Required Arguments | | None |
| Optional Arguments | | None |
| Extra Arguments Ignored | | True |
| Response Format | | json |
| Notes | | Sample Response: {
"status": "200 OK",
"code": "/api/status/ok"
}
For additional information on using the callback parameter to generate a JSONP response, or using onsucceed and onfail to redirect to a URI template, see Common API Query Parameters. |
