greptilian logo

IRC log for #rest, 2016-07-05

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:28 tbsf joined #rest
00:51 tbsf joined #rest
01:04 fuzzyhorns joined #rest
01:05 tbsf joined #rest
01:43 fuzzyhorns joined #rest
03:16 fuzzyhorns joined #rest
06:00 Macaveli joined #rest
06:05 _ollie joined #rest
06:28 vanHoesel joined #rest
07:14 _ollie joined #rest
07:18 Coldblackice_ joined #rest
07:22 itscaleb joined #rest
07:22 wsieroci joined #rest
07:30 Tomatosoup1 joined #rest
07:53 interop_madness joined #rest
08:26 graste joined #rest
09:00 Davey left #rest
09:08 _ollie joined #rest
10:05 wsieroci joined #rest
10:14 sbeex joined #rest
10:15 sbeex Hello !
10:16 sbeex I have a small question regarding REST good pratices. When you do an update of an existing object (say we have : PUT user/32 user{id: 32, username: "john"}. Why do we send 2 times the id ? thank you in advance
10:18 trygvis you have to ask the person who created you API about that
10:19 trygvis but usually it follows the principle of updating the *entire* state of the resource
11:01 sbeex I am the owner of the api so here come my question :) what should I do :p
11:09 _ollie joined #rest
11:10 shodan` joined #rest
12:55 Tomatosoup1 joined #rest
13:11 saml joined #rest
13:36 trygvis I'm trying another direction with my search/type thing
13:36 trygvis instead of including rel=type, href=url in the hal resources I'm letting the search result have one set of embedded resources per type
13:36 trygvis that is a pattern we already use when listing all contacts
15:11 fuzzyhorns joined #rest
15:28 tbsf joined #rest
15:57 vanHoesel joined #rest
16:09 Coldblackice_ joined #rest
16:48 wsieroci joined #rest
17:24 vanHoesel joined #rest
17:34 Tomatosoup1 joined #rest
17:39 graste joined #rest
18:00 Devastator_ joined #rest
18:09 vanHoesel joined #rest
18:16 fuzzyhorns joined #rest
18:31 Devastator_ joined #rest
18:40 vanHoesel joined #rest
19:33 mamund joined #rest
20:58 Tomatosoup1 joined #rest
21:25 fuzzyhorns joined #rest
21:59 k_j joined #rest
21:59 k_j hi
22:00 Tomatosoup1 hi
22:02 k_j i am trying to design a simple rest api for my application. now the aspect i am dealing with is the /settings resource.  My application has a number of settings which can (probabably) be better set with PUT (rather than POST). Settings can be logically divided in three groups, say "generic", "proxy", "user".     is it ok to implement  PUT on /settings/global  , /settings/proxy and  /settings/user and a GET on /settings to retrive all the settings?
22:41 whartung sure, why not?
23:21 pdurbin it's a free country

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

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