greptilian logo

IRC log for #rest, 2018-06-29

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

| Channels | #rest index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

All times shown according to UTC.

Time S Nick Message
00:30 philbot joined #rest
00:30 Topic for #rest is now #rest REpresentational State Transfer | logs: http://irclog.greptilian.com/rest/today |  http://tech.groups.yahoo.com/group/rest-discuss | http://code.google.com/p/implementing-rest/ | http://en.wikipedia.org/wiki/Representational_State_Transfer
00:32 pdurbin joined #rest
05:34 donofrio joined #rest
09:09 interop_madness joined #rest
09:18 Haudegen joined #rest
11:06 interop_madness joined #rest
13:33 Haudegen joined #rest
14:35 wsieroci joined #rest
14:53 wsiqueir joined #rest
15:04 zama joined #rest
15:05 igitoor joined #rest
15:15 igitoor joined #rest
16:01 cornbread joined #rest
16:14 tellnes joined #rest
18:29 Haudegen joined #rest
19:29 wsieroci joined #rest
19:54 saml__ hello
19:54 saml__ can representation change?  as in, client would need to poll
19:54 saml__ or is this plain bad design?
20:00 saml_ joined #rest
20:57 whartung saml_: what do you mean can representation change?
21:14 saml_ whartung, like {"status":"created"}   and some time later, same GET will have different body
21:15 whartung well, there’s nothing wrong with that. Your clients may complain, but that’s a versioning issue. Kind of all depends on the specificy of your content-type
21:16 saml_ ah i see

| Channels | #rest index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

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