IRC log for #rest, 2014-06-17

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

All times shown according to UTC.

Time	Nick	Message
00:50		DrCode joined #rest
00:58		DrCode joined #rest
02:46		wilmoore joined #rest
03:01		Creeves joined #rest
03:01		Creeves left #rest
03:59	chovy	tmoore: well with most apis i've used, the requests assume authentication is required and they don't all hang off /api/users/:id/*
03:59	chovy	what i'm doing is public data for a user that any user can request will be accessible from /api/users/:id/foo but something specific to logged in user will just be /api/whatever
07:07	tmoore	chovy: got that part... what's the difficulty?
07:08		_ollie joined #rest
07:11	chovy	tmoore: i'm just trying to figure out best way to do it.
07:50		graste joined #rest
08:03		ph88_ joined #rest
08:20		licyeus joined #rest
08:20		nardbard joined #rest
08:20		gluegadget joined #rest
08:20		bigbluehat joined #rest
08:20		asm89 joined #rest
08:20		ekroon joined #rest
08:20		HighBit joined #rest
08:20		vlakarados joined #rest
08:20		mmun joined #rest
08:20		whartung joined #rest
08:20		ph88_ joined #rest
08:20		graste joined #rest
08:20		_ollie joined #rest
08:20		DrCode joined #rest
08:20		saml joined #rest
08:20		ssedano joined #rest
08:20		daxim joined #rest
08:20		elnur joined #rest
08:20		pindonga joined #rest
08:20		Jarda joined #rest
08:20		blongden joined #rest
08:20		rickharrison joined #rest
08:20		danfinch joined #rest
08:20		chovy joined #rest
08:20		brainproxy joined #rest
08:20		igitoor joined #rest
08:20		ederign joined #rest
08:20		Davey joined #rest
08:20		KarlHungus joined #rest
08:20		pdurbin joined #rest
08:20		trygvis joined #rest
08:20		`0660 joined #rest
08:20		dD0T joined #rest
08:20		asdf` joined #rest
08:20		alxbl joined #rest
08:20		ramsey joined #rest
08:20		riddle joined #rest
08:20		gamache joined #rest
08:36		wilmoore joined #rest
08:42		whartung joined #rest
08:42		HighBit joined #rest
08:42		ekroon joined #rest
08:42		asm89 joined #rest
08:42		bigbluehat joined #rest
08:42		gluegadget joined #rest
08:42		nardbard joined #rest
08:42		licyeus joined #rest
08:42		vlakarados joined #rest
08:42		mmun joined #rest
09:11		rincewind joined #rest
09:13	rincewind	hi! whats the general opinion about making a patch on one property on a resource that affects other properties on that resource?
09:14	rincewind	e.g patch one property, and when getting that resource again other properties have changed as well
09:24		shrink0r joined #rest
09:29		rosstuck joined #rest
09:31		DrCode joined #rest
09:41		shrink0r1 joined #rest
10:08		_ollie joined #rest
11:56	tmoore	rincewind: I think that's pretty common
11:57	rincewind	thx
11:57	tmoore	it's handy to respond to requests that change a resource with a full, up-to-date representation of the resource
11:57	rincewind	sounds fair
11:57	tmoore	then the client can use that to re-sync it's internal state
11:58	rincewind	is it common to use json pointers for a patch according to you?
11:59	rincewind	http://tools.ietf.org/html/rfc6902
12:15	tmoore	rincewind: I don't really know tbh but I think that spec is pretty new and not that commonly deployed yet
12:16	tmoore	it seems like a pretty good idea to me, but I've never actually implemented it mysefl
12:16	tmoore	s/mysefl/myself/
12:23	rincewind	ok, thx for the info
13:59		m0ltar joined #rest
14:39		fumanchu joined #rest
14:42		m0ltar joined #rest
15:13		shrink0r joined #rest
15:50		_ollie joined #rest
16:08		wilmoore joined #rest
16:11		spaceone joined #rest
16:12	spaceone	is http/2 still a protocol to implement REST? it is not stateless afaics
16:18	pdurbin	good question. no answer at http://http2.github.io/faq/
16:18	spaceone	^^
16:18	spaceone	maybe i should ask at the mailing list
16:19	spaceone	i would also like to know how long it will take that the http/2 standard rfc will be released
16:20	* fumanchu	hopes about 5 years and several hundred revisions from real experience
16:20	spaceone	i hope it will take some years
16:20	spaceone	the implementation of http2 is so much more complex than http1
16:26	trygvis	spaceone: uhm, how is http2 not stateless?
16:28	spaceone	it creates a session and doesn't send headers again
16:29	spaceone	first request contains every headers, second request doesn't contain these headers
16:37	trygvis	I think you're misunderstanding how that is supposed to work. it's an optimalization, the server and client won't notice if the connection dies and the next request is done in a new connection
16:37	trygvis	semanticly, the server is getting all the headers in every request
16:40	spaceone	the server == the application → yes... the bytes aren't transferred again
16:41	trygvis	right, but that doesn't make http/2 stateful
16:41	spaceone	if that is OK for REST → great, then the list of disadvantages can be reduced
16:42	spaceone	it makes the implementation stateful
16:42	trygvis	http/1.1 has persistent connection, that still doesn't make http/1.1 stateful. it's still messages flowing, same with http/2
16:42	trygvis	I'm out for now
16:43	spaceone	okay
16:43	spaceone	i just wanted to be sure
16:50	spaceone	what is meant by 'coordinated' in "An architectural style is a named, coordinated set of architectural constraints." ?
16:51	_ollie	spaceone: the constrains are usually related to each other…
16:53	spaceone	aight
16:54		DracoBlue joined #rest
16:58		Left_Turn joined #rest
17:11		chovy left #rest
17:32		DracoBlue joined #rest
17:39		graste joined #rest
17:52		therabidbanana joined #rest
17:53		ph88 joined #rest
17:59		_ollie joined #rest
18:10		rincewind3 joined #rest
18:11	spaceone	what would be an example of a non client-server architecture?
18:32	whartung	an application where the application and the database are the same application, where the db is embedded and part of the application spaceone
18:32	spaceone	whartung: yes, but what do you call this architecture?
18:32	spaceone	how?
18:33	whartung	I dunno, monolithic application?
18:33	whartung	since most everything save desk top calculators are client server, it's hard to imagine any more lol
18:33	spaceone	^^
18:34	spaceone	also isn't a application like you told not also client-server? (GUI/CLI - unix/tcp socket - database)
18:35	spaceone	hm, maybe a sqlite database is a good example for that application
18:36	whartung	yea, sqlite is (can be) just a linked library
18:36	whartung	it's no more client server than strlen is
18:36	spaceone	yep
18:36		shrink0r joined #rest
18:48		fumanchu joined #rest
18:52		fumanchu_ joined #rest
18:53	saml	flappy bird is not client server
18:54	saml	emacs is client server
19:00		m0ltar joined #rest
19:21	spaceone	what would be an example of implicit as cacheable labelled data?
19:27		mmun left #rest
19:28		wilmoore joined #rest
20:15		wilmoore joined #rest
20:18		wilmoore joined #rest
20:18		vlakarados joined #rest
20:18		licyeus joined #rest
20:18		nardbard joined #rest
20:18		gluegadget joined #rest
20:18		bigbluehat joined #rest
20:18		asm89 joined #rest
20:18		ekroon joined #rest
20:18		HighBit joined #rest
20:35		whartung joined #rest
21:17		m0ltar joined #rest
21:42		fumanchu joined #rest
21:45		charlex joined #rest
21:55		_ollie joined #rest

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