IRC log for #rest, 2014-07-14

https://trygvis.io/rest-wiki/

All times shown according to UTC.

Time	Nick	Message
06:34		rosstuck joined #rest
07:15		wilmoore joined #rest
07:48		ph88 joined #rest
08:05		graste joined #rest
09:00		_ollie joined #rest
12:18		danizord joined #rest
12:32		danizord joined #rest
12:51		martinfilliau joined #rest
13:11		_ollie joined #rest
13:35		shrink0r joined #rest
13:38		charlie joined #rest
13:48		saml joined #rest
14:26		_ollie joined #rest
14:30		nkoza joined #rest
14:36		seanbrant joined #rest
14:47	seanbrant	im having trouble finding advice on how to represent deletes. the use-case is a ios app maintains a local cache of content from my api. when content gets deleted the ios app needs to know this so it can remove it from its local copy. on solution is to just re-download the entire dataset and do a diff. this works for smallish datasets but for large ones its not good. in the past i’ve returned the “deleted” version of the resource (just id and a statu
14:47	seanbrant	deleted). this way you could ask the api give me everything modified since X and it would return including deleted stuff. this works but im just wondering if anyone knows of any document solutions to this problem
14:49	saml	what's wrong with /diff resource?
14:49	saml	GET /diff?my-content=<checksum of all your contents> ?
14:50	saml	then it gives you added, modified, deleted resources
14:50	saml	if there's authentication, you don't need that query string
14:50	saml	since the api knows who you are
14:50	saml	wait..
14:51	saml	client still needs to supply current status of its cache
14:51	seanbrant	saml: i think the client would need to send all the ids of the content it has. this might be alot of ids
14:51	saml	maybe do logs
14:52	saml	GET /logs?since=<last-time-you-checked>
14:52	saml	and api gives you what happened since you last checked
14:52	saml	and client can update cache accordingly
14:52	seanbrant	saml: one idea was a flag on the resource for just getting deletions since, which is kind of like the log idea
14:53	saml	very similar to conditional requests using Last-Modified and Etags
14:53		_ollie joined #rest
14:53	seanbrant	saml: logs is a cool idea as it could be used for creations and updates as well
14:54	seanbrant	the client can just replay the logs against its own database
14:54	saml	yah. updates could be tricky if you want to actually implement diff/patch
14:54	seanbrant	true
14:54	saml	or just re-download updated (like git)
14:54	saml	like git checkout
14:55	saml	instead of getting changeset from api and apply to client cache
14:55	saml	there could be already some convention or standard or library for this kind of stuff
14:55	saml	maybe webdav
15:31		interop_madness joined #rest
15:32		charlie_ joined #rest
15:55		seanbrant joined #rest
16:39		danizord joined #rest
16:44		wilmoore joined #rest
16:46		DrCode joined #rest
16:50		ph88_ joined #rest
17:13		matt444 joined #rest
17:13	matt444	hello.. what's it called when an API always returns the same thing for GET?
17:14	matt444	i can't think of the word
17:15		matt444 left #rest
17:15		graste joined #rest
17:16	asdf`	'static', but i think he meant idempotent
17:16	asdf`	or eh, 'cached' :)
17:40		seanbrant joined #rest
17:50		_ollie joined #rest
18:33		_ollie joined #rest
18:39		_ollie joined #rest
18:49		seanbrant joined #rest
19:15		_ollie joined #rest
19:57		_ollie joined #rest
20:10		_ollie joined #rest
20:30		_ollie joined #rest
20:35		_ollie joined #rest
20:42		shrink0r joined #rest
20:43		_ollie joined #rest
21:22		_ollie joined #rest
21:28		_ollie joined #rest
21:59		_ollie joined #rest
22:19		_ollie joined #rest
22:25		shrink0r left #rest
22:27		_ollie joined #rest
22:57		_ollie joined #rest
23:12		_ollie joined #rest
23:42		_ollie joined #rest
23:49		_ollie joined #rest

https://trygvis.io/rest-wiki/