| Time |
S |
Nick |
Message |
| 00:04 |
|
pdurbin |
:) |
| 00:29 |
|
|
blahdeblah joined #rest |
| 00:29 |
|
|
blahdeblah joined #rest |
| 01:53 |
|
|
_ollie1 joined #rest |
| 02:10 |
|
|
jcromartie joined #rest |
| 02:12 |
|
* fumanchu |
will join #rpc when he works for an enterprise again |
| 02:48 |
|
pdurbin |
:) |
| 03:49 |
|
|
lemur joined #rest |
| 05:47 |
|
|
rosstuck joined #rest |
| 09:53 |
|
|
Left_Turn joined #rest |
| 09:57 |
|
|
mezod joined #rest |
| 11:29 |
|
|
jcromartie joined #rest |
| 11:33 |
|
pdurbin |
http://restlet.com/blog/2015/03/20/this-week-in-api-land/ |
| 11:34 |
|
pdurbin |
http://restlet.com/blog/2015/03/27/this-week-in-api-land-take-2/ |
| 11:34 |
|
|
warehouse13 joined #rest |
| 11:37 |
|
pdurbin |
https://blogs.dropbox.com/developers/2015/03/limitations-of-the-get-method-in-http/ |
| 11:38 |
|
pdurbin |
heh. "Level 0: RTFM" http://apihandyman.io/hypermedia-api-maturity-model-part-i-hypermedia-ness/ |
| 11:52 |
|
pdurbin |
https://medium.com/@etiennerouzeaud/how-to-create-a-basic-restful-api-in-go-c8e032ba3181 |
| 12:07 |
|
|
philbot joined #rest |
| 12:07 |
|
|
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 |
| 12:24 |
|
|
_ollie joined #rest |
| 14:16 |
|
|
mezod joined #rest |
| 14:28 |
|
|
_ollie1 joined #rest |
| 15:09 |
|
|
wsiqueir-call joined #rest |
| 15:25 |
|
asdf` |
so i'm wondering about implementing software that consumes a rest api; generic clients are of course very easy, but what about specific clients? for example, i want a 'customers' list in my main menu, and when i examine one of them, that shows a 'products this customer bought' list; i need to know this menu structure beforehand so that i can script and style it, so discoverability kinda doesn't help here? |
| 15:25 |
|
asdf` |
is that a trivial issue, a no-issue or an actual issue? |
| 15:31 |
|
trygvis |
the client need to learn the relations it needs to accomplish it's task |
| 15:34 |
|
asdf` |
sure, but i mean, what if one of the resources needs to be displayed very differently from all the others? |
| 15:35 |
|
asdf` |
hmm, that's where this 'code-on-demand' thing comes in handy, isn't it |
| 15:35 |
|
trygvis |
hm, how is that a problem for the REST interactions? |
| 15:36 |
|
trygvis |
that depends, most machine-to-machine communication doesn't involve/care much about how stuff looks |
| 15:38 |
|
asdf` |
well that's not a problem of rest interactions, it's a problem of non-generic clients |
| 16:48 |
|
|
quimrstorres joined #rest |
| 17:18 |
|
|
tr3online joined #rest |
| 17:24 |
|
|
tr3online joined #rest |
| 18:32 |
|
|
_ollie joined #rest |
| 19:29 |
|
|
lemur_ joined #rest |
| 20:27 |
|
|
quimrstorres joined #rest |
| 20:31 |
|
|
quimrstorres joined #rest |
| 20:38 |
|
|
quimrstorres joined #rest |
| 20:46 |
|
|
quimrstorres joined #rest |
| 21:06 |
|
|
quimrstorres joined #rest |
| 21:25 |
|
|
quimrsto_ joined #rest |
| 21:30 |
|
|
trygvis joined #rest |
| 21:31 |
|
|
asm89 joined #rest |
| 21:32 |
|
|
quimrstorres joined #rest |
| 21:47 |
|
|
_ollie1 joined #rest |
| 22:13 |
|
|
quimrstorres joined #rest |
| 23:00 |
|
|
fumanchu_ joined #rest |
| 23:33 |
|
|
quimrstorres joined #rest |
| 23:33 |
|
|
fumanchu joined #rest |
| 23:42 |
|
|
quimrstorres joined #rest |
