IRC log for #rest, 2016-07-02

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

All times shown according to UTC.

Time	Nick	Message
00:31		tbsf joined #rest
02:24		tbsf joined #rest
02:29		fuzzyhorns joined #rest
03:40		tbsf joined #rest
04:31		tbsf joined #rest
05:01		upasana joined #rest
07:25		ShekharReddy joined #rest
07:33		Davey joined #rest
07:33		Davey joined #rest
10:26		wsieroci joined #rest
10:29		wsieroci joined #rest
12:37		_ollie joined #rest
13:46		graste joined #rest
14:15		tbsf joined #rest
14:33		tbsf joined #rest
14:51		wsieroci_ joined #rest
15:09		ShekharReddy joined #rest
15:27		tbsf joined #rest
15:34		graste joined #rest
15:56		tbsf joined #rest
16:15		Tomatosoup1 joined #rest
16:15	Tomatosoup1	Roy Fielding's dissertation was written in context of HTTP 1.1 - what about HTTP/2 ? are there any changes in architectural style ?
16:19		ShekharReddy joined #rest
16:29		_ollie joined #rest
18:16		Tomatosoup joined #rest
18:40		fuzzyhorns joined #rest
18:56		Devastator joined #rest
20:25		wsieroci_ joined #rest
21:41		fuzzyhorns joined #rest
22:13	mamund	Tomatosoup: you still there? i don't see anything changing in his style (15 yrs old now).
22:15	Tomatosoup	mamund: yep, im still here
22:15	mamund	esp. since his style spans other protocols like CoAP.
22:15	mamund	Fielding also has talked about another protocol design called WAKA that he sez matches his style better.
22:15	mamund	someday we might see that<g>
22:16	mamund	HTTP2 is really, IMO, an optimization. binary is the default, compression on the headers, SSL is preferred.
22:17	mamund	no new methods, not changes to the way conneg works, authneg, encoding, etc.
22:17	mamund	that's my POV anyway.
22:18	Tomatosoup	that is basically what i thought, the underlying architecture of protocol is pretty much the same, lots of optimization, as you said
22:19	mamund	after close to 25 years of HTTP, i think there is not much likelihood of any breakout changes to the protocol.
22:19	mamund	instead, we'll "fork it" and create new ones (like CoAP, really).
22:21	Tomatosoup	CoAP - it is subsitute for HTTP ?
22:24	mamund	not a substitute, but i think of it as a follow-on or sequel<g>
22:25	mamund	uses UDP, binary msgs, and the msgs are quite short (4k max, i think). designed for low power, small deivce, IOT-stype stuff.
22:25	mamund	anyway, has almost all the hallmarks of FIelding'
22:25	mamund	Fielding's REST style but over UDP.
22:26	mamund	https://tools.ietf.org/html/rfc7252
22:30	Tomatosoup	that is interesting
22:31	Tomatosoup	what about usage, since it is UDP ? Restful conferences ?
22:32	mamund	??
22:32	Tomatosoup	that was just silly statement :P but i just wonder when it is usefull since it is via UDP
22:32	mamund	ahhh
22:33	mamund	well, broadcasting to lots of low-power devices is a great use-case for UDP.
22:33	Tomatosoup	well, im aware of UDP protocol, but im talking about any changes beacuse od CoAP
22:33	Tomatosoup	it is worth changing ?
22:34	mamund	well, CoAP is not a replacement for HTTP, it's a fork for a diff set of use-cases.
22:35	mamund	if you find yourself doing lots of IoT, i think CoAP can make sense.
22:35	Tomatosoup	you know what, i guess my questions are just silly
22:35	Tomatosoup	i will spend some time reading about CoAP
22:36	Tomatosoup	and then maybe ask for something :)
22:36	mamund	LOL!
22:36	mamund	often doing beats asking, eh?
22:36	mamund	http://www.herjulf.se/download/coap-2013-fall.pdf
22:36	mamund	not sure how accurate this is anymore (from 2013) but one of my "go to" decks when ppl ask
22:37	Tomatosoup	what you mean by "beats asking" ?:P
22:40	Tomatosoup	mamund: i still dont quite get what does 'betas asking' mean :P
22:40	Tomatosoup	*beats
22:41	Tomatosoup	nvm, just didnt know this phrasal verb (or idiom, whatever)
22:45	Tomatosoup	thanks anyway
22:46	Tomatosoup	btw mamund, would you recommand me must-read position about REST ?
23:46		fuzzyhorns joined #rest

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