Time |
S |
Nick |
Message |
00:00 |
|
|
fuzzyhorns joined #rest |
00:01 |
|
|
fuzzyhorns joined #rest |
00:02 |
|
|
fuzzyhorns joined #rest |
00:03 |
|
|
fuzzyhorns joined #rest |
00:04 |
|
|
fuzzyhorns joined #rest |
00:05 |
|
|
fuzzyhorns joined #rest |
00:06 |
|
|
fuzzyhorns joined #rest |
00:07 |
|
|
fuzzyhorns joined #rest |
00:08 |
|
|
fuzzyhorns joined #rest |
00:09 |
|
|
fuzzyhorns joined #rest |
00:10 |
|
|
fuzzyhorns joined #rest |
00:11 |
|
|
fuzzyhorns joined #rest |
00:12 |
|
|
fuzzyhorns joined #rest |
00:13 |
|
|
fuzzyhorns joined #rest |
00:14 |
|
|
fuzzyhorns joined #rest |
01:21 |
|
|
Coldblackice joined #rest |
04:21 |
|
|
mamund_ joined #rest |
04:32 |
|
|
mamund_ joined #rest |
05:45 |
|
|
mamund_ joined #rest |
06:10 |
|
|
mamund_ joined #rest |
06:59 |
|
|
Coldblackice_ joined #rest |
07:14 |
|
|
Macaveli joined #rest |
07:42 |
|
|
Macaveli joined #rest |
07:46 |
|
|
_ollie joined #rest |
07:47 |
|
|
Tomatosoup1 joined #rest |
08:44 |
|
|
graste joined #rest |
09:11 |
|
|
tbsf joined #rest |
09:27 |
|
|
mamund_ joined #rest |
10:15 |
|
|
timg__ joined #rest |
11:47 |
|
|
shodan` joined #rest |
12:22 |
|
|
mamund_ joined #rest |
12:58 |
|
|
averagedan joined #rest |
12:58 |
|
averagedan |
hi |
12:59 |
|
pdurbin |
averagedan: hi |
12:59 |
|
averagedan |
making a REST API for a project between my friends, basically there's entries and comments on those entries.. if I have the /entries/ID endpoint, should I return the comments with that, or should I make a different endpoint for that, like, /entries/ID/comments? |
13:00 |
|
Tomatosoup1 |
the latter |
13:00 |
|
Tomatosoup1 |
each resource should have its own URI |
13:01 |
|
Tomatosoup1 |
so getting one comment would be through /entries/{entry_id}/comments/{comment_id} |
13:04 |
|
averagedan |
mhm |
13:04 |
|
averagedan |
interesting |
13:05 |
|
averagedan |
let's say i'm storing votes for the entries in a seperate table, and i'd like to calculate those per entry, and return them. i assume I should just add a 'score' field to the 'entries/ID endpoint, right? |
13:26 |
|
|
Macaveli joined #rest |
14:09 |
|
|
fuzzyhorns joined #rest |
14:34 |
|
|
Devastator joined #rest |
14:35 |
|
|
firemark joined #rest |
14:43 |
|
|
firemark joined #rest |
14:48 |
|
|
ShekharReddy joined #rest |
14:48 |
|
|
firemark_ joined #rest |
15:13 |
|
|
ShekharReddy joined #rest |
15:46 |
|
|
wsieroci joined #rest |
15:58 |
|
|
tbsf joined #rest |
16:04 |
|
|
Tomatosoup1 joined #rest |
16:04 |
|
|
Coldblackice_ joined #rest |
16:44 |
|
|
wsieroci joined #rest |
16:46 |
|
whartung |
this in interesting |
16:46 |
|
whartung |
https://www.infoq.com/news/2016/07/microsoft-rest-api |
17:44 |
|
|
fuzzyhorns joined #rest |
18:01 |
|
|
mamund_ joined #rest |
18:02 |
|
* mamund_ |
steps in |
18:05 |
|
|
Devastator_ joined #rest |
18:10 |
|
mamund_ |
sorry, lost connection and am not sure if this was already posted: |
18:10 |
|
mamund_ |
https://www.infoq.com/news/2016/07/microsoft-rest-api |
18:10 |
|
mamund_ |
InfoQ peice w/ Fielding's response to the MSFT Guidelines doc |
18:29 |
|
|
wsieroci joined #rest |
18:42 |
|
|
mamund__ joined #rest |
18:43 |
|
whartung |
yea I posted that earlie mamund |
18:43 |
|
whartung |
2 hrs ago |
18:44 |
|
|
fuzzyhorns joined #rest |
18:47 |
|
mamund__ |
cool, thanks whartung |
18:48 |
|
whartung |
I even chimed in in the commentary lol |
18:48 |
|
whartung |
SImilarly, I just LOVE this, from another article on infoq: "HTTP-RPC is a lightweight open-source framework for developing RESTful applications using an RPC metaphor" |
18:48 |
|
whartung |
/facepalm |
18:49 |
|
whartung |
just proves my point |
18:49 |
|
|
fuzzyhorns joined #rest |
19:14 |
|
|
mamund_ joined #rest |
19:16 |
|
|
Devastator_ joined #rest |
19:16 |
|
|
Devastator left #rest |
19:24 |
|
|
graste joined #rest |
19:29 |
|
|
Coldblackice_ joined #rest |
19:32 |
|
|
foist_ joined #rest |
21:18 |
|
|
mamund_ joined #rest |
21:19 |
|
|
mamund joined #rest |
21:43 |
|
|
tbsf joined #rest |
21:44 |
|
|
fuzzyhorns joined #rest |
21:53 |
|
|
tbsf joined #rest |
22:32 |
|
|
fuzzyhorns joined #rest |
22:34 |
|
|
tbsf joined #rest |
22:35 |
|
|
tbsf joined #rest |
22:46 |
|
|
firemark joined #rest |
23:09 |
|
|
firemark_ joined #rest |
23:45 |
|
|
shodan` joined #rest |
23:46 |
|
shodan` |
What would be the best route to quickly get for example a user's group. The group has a lot of sub routes so doing /users/me/group/dothing feels silly |
23:47 |
|
shodan` |
since it'll just be an alias for /groups/{id}/dothing |
23:59 |
|
whartung |
what do you mean "group has a lot of sub routes" |