canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,093
edits
Labs/Bespin/ServerAPI: Difference between revisions
Jump to navigation
Jump to search
→Editing: changing /edit/reset to POST because of its data changing properties
(→Editing: disambiguating the PUT /edit/ with /at/ just like we did with /file/) |
(→Editing: changing /edit/reset to POST because of its data changing properties) |
||
| Line 17: | Line 17: | ||
* GET /edit/recent/N/[path] gives a JSON list of edit actions, starting after N. edit/recent/1 would skip the first entry. | * GET /edit/recent/N/[path] gives a JSON list of edit actions, starting after N. edit/recent/1 would skip the first entry. | ||
* PUT /edit/at/[path], with the serialized JSON object representing the action as the PUT body. (you can start sending do's before your first save.) | * PUT /edit/at/[path], with the serialized JSON object representing the action as the PUT body. (you can start sending do's before your first save.) | ||
* | * POST /edit/reset/ blows away all edits | ||
* | * POST /edit/reset/[path] blows away edits for a specific path | ||
* edit queue is wiped when file is saved. (otherwise someone GETting the file and edits has no way of knowing the original state of the file from which to start applying edit actions) | * edit queue is wiped when file is saved. (otherwise someone GETting the file and edits has no way of knowing the original state of the file from which to start applying edit actions) | ||