Timeline for A separate endpoint specifically for sync in a REST api
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 1, 2015 at 19:54 | answer | added | Ramesh | timeline score: 0 | |
| Dec 8, 2014 at 22:31 | answer | added | MichelHenrich | timeline score: 0 | |
| Dec 8, 2014 at 20:55 | answer | added | Jonathan Eunice | timeline score: 2 | |
| Dec 8, 2014 at 17:08 | comment | added | Mike Partridge | I'll add the obligatory "are you sure this is a necessary optimization?" As @Cormac points out, caching may do everything you need if you set headers properly in your requests and responses. | |
| Dec 8, 2014 at 16:42 | answer | added | Cormac Mulhall | timeline score: 1 | |
| Dec 2, 2014 at 9:44 | vote | accept | iTwenty | ||
| Dec 2, 2014 at 9:44 | vote | accept | iTwenty | ||
| Dec 2, 2014 at 9:44 | |||||
| Dec 2, 2014 at 9:44 | comment | added | iTwenty | That's good to know, but I don't yet need changes to be delivered to me in real time. | |
| Dec 2, 2014 at 8:11 | comment | added | Luc Franken | Http has upgrade commands which allow the client to upgrade the connection from a simple request to for example a stream. developer.mozilla.org/en-US/docs/Web/HTTP/… So for example if you make a list with all changes (audits) you can do: GET /audits/userid and then upgrade the connection to like a stream to stay up to date. | |
| Dec 2, 2014 at 6:39 | answer | added | sea-rob | timeline score: 1 | |
| Dec 2, 2014 at 6:25 | review | First posts | |||
| Dec 2, 2014 at 7:49 | |||||
| Dec 2, 2014 at 6:20 | history | asked | iTwenty | CC BY-SA 3.0 |