| Time |
S |
Nick |
Message |
| 00:22 |
|
|
fuzzyhorns joined #rest |
| 02:39 |
|
|
baweaver joined #rest |
| 02:48 |
|
|
fuzzyhorns joined #rest |
| 06:34 |
|
|
_ollie joined #rest |
| 07:11 |
|
|
rosstuck joined #rest |
| 07:21 |
|
|
wsiqueir joined #rest |
| 07:55 |
|
|
quimrstorres joined #rest |
| 08:18 |
|
|
graste joined #rest |
| 08:33 |
|
|
quimrstorres joined #rest |
| 08:45 |
|
|
quimrstorres joined #rest |
| 08:50 |
|
|
darkangel joined #rest |
| 08:52 |
|
darkangel |
For updates, is it not good to use PATCH unless you use json patch (i.e. sets of operations) instead of just "key: value" updates? This article seems to suggest so: http://williamdurand.fr/2014/02/14/please-do-not-patch-like-an-idiot/ |
| 08:54 |
|
trygvis |
you don't have to use rfc6902, but you should use *some* patch format |
| 08:55 |
|
trygvis |
it's the same arguments as for why you shouldn't use application/json in your APIs but a particular hypermedia |
| 08:56 |
|
darkangel |
trygvis: Is this easy to do from a JavaScript client? I hope there are libs for this. :) |
| 09:06 |
|
darkangel |
I found some libs, now I need to check for server-side support. :) |
| 12:07 |
|
pith |
trygvis: which format do you recommend for hypermedia ? |
| 12:07 |
|
pith |
Does anyone use JSON-HOME and HAL ? |
| 12:13 |
|
pdurbin |
https://trygvis.io/rest-wiki/hypermedia/collection-json/ I assume |
| 12:13 |
|
trygvis |
I like collection+json, but I've used HAL a lot too |
| 12:18 |
|
pith |
personally I use HAL in combination to JSON-HOME, and I was wondering if it's a good practice to always add in the resource's links a link to the API entry point (the JSON-HOME resource in my case) |
| 13:20 |
|
|
Left_Turn joined #rest |
| 13:37 |
|
|
quimrstorres joined #rest |
| 14:47 |
|
|
wsiqueir joined #rest |
| 15:14 |
|
|
fadeway joined #rest |
| 15:16 |
|
fadeway |
if my GET query requires too long paramaters to fit in the url, how bad is it to implement it as a POST instead? |
| 15:17 |
|
pdurbin |
why would it be bad? |
| 15:18 |
|
|
fuzzy_horns joined #rest |
| 15:18 |
|
fadeway |
It's a POST that doesn't change anything on the server |
| 15:18 |
|
fuzzy_horns |
im a little scared to ask, but im trying to put together a presentation for my work, and wondered if anyone had any feedback |
| 15:18 |
|
fuzzy_horns |
http://mooreniemi.github.io/hypermedia-presentation/#/ |
| 15:21 |
|
pdurbin |
fadeway: sounds like you can't use GET though |
| 15:21 |
|
fadeway |
pdurbin: yeah, exactly, I don't want to be unrestful but I also don't see another way |
| 15:22 |
|
pdurbin |
if you can't use GET you can't use GET |
| 15:23 |
|
pdurbin |
fuzzy_horns: looks good. ship it :) |
| 15:24 |
|
fuzzy_horns |
:) |
| 15:24 |
|
fumanchu_ |
fuzzy_horns: that looks GREAT. well done. |
| 15:26 |
|
fuzzy_horns |
thanks guys :) what a confidence booster, your opinions mean a ton to me |
| 15:26 |
|
fuzzy_horns |
ive learned a lot from this chan! |
| 15:45 |
|
pdurbin |
me too |
| 15:51 |
|
asdf` |
fuzzy_horns, on page 23 the red text says 'HTTP' while i think you meant 'HTML' |
| 15:53 |
|
|
fadeway left #rest |
| 16:13 |
|
|
ramsey joined #rest |
| 16:39 |
|
|
baweaver joined #rest |
| 16:46 |
|
fuzzy_horns |
asdf`: ahh i really meant "from http" |
| 16:46 |
|
fuzzy_horns |
that is confusing, thanks |
| 16:58 |
|
|
ModusPwnens joined #rest |
| 17:03 |
|
ModusPwnens |
I have ServiceA that manages ResourceA. I also have ServiceB that manages ResourceB. ResourceB has a subresource of ResourceA. There is a particular workflow that can occur where if ResourceA is updated, ResourceB must also be updated. How does one do this RESTfully? |
| 17:04 |
|
whartung |
PUT .../ResourceA followed by PUT .../ResourceB |
| 17:07 |
|
fumanchu_ |
yep |
| 17:07 |
|
fumanchu_ |
and use workflow rather than transactions to fix if things go wrong |
| 17:09 |
|
fumanchu_ |
https://www.google.com/search?q=helland%20life%20beyond%20distributed%20transactions |
| 17:10 |
|
whartung |
heh -- I must have visited that paper before…I just don't recall it. |
| 17:12 |
|
fumanchu_ |
it really filled in for me the scalability reasons why REST is the way it is |
| 17:14 |
|
whartung |
I'll dance joyous in the rain when Academia(™) learns that the two column journal format is long past dated. |
| 17:17 |
|
fuzzy_horns |
whartung: in the mean time k2pdfopt |
| 17:17 |
|
whartung |
? |
| 17:17 |
|
|
rickharrison joined #rest |
| 17:24 |
|
darkangel |
fuzzy_horns: "mumciplaity" :D @ http://mooreniemi.github.io/hypermedia-presentation/#/13/1 |
| 17:28 |
|
whartung |
are those sloths that melted together, or is that prop from "The Thing"? |
| 17:28 |
|
whartung |
*a prop |
| 17:29 |
|
asdf` |
most of the props in 'The Thing' were in fact sloths that melted together |
| 17:30 |
|
whartung |
:) |
| 17:52 |
|
fuzzy_horns |
darkangel: lol and terrifyingly that is a real example too! |
| 17:52 |
|
darkangel |
fuzzy_horns: Yikes :) |
| 17:58 |
|
|
darkangel left #rest |
| 18:58 |
|
|
fumanchu joined #rest |
| 19:00 |
|
|
fumanchu1 joined #rest |
| 19:03 |
|
|
quimrstorres joined #rest |
| 19:31 |
|
|
quimrstorres joined #rest |
| 19:48 |
|
|
fuzzy_horns joined #rest |
| 19:49 |
|
|
fumanchu joined #rest |
| 19:52 |
|
|
quimrstorres joined #rest |
| 19:57 |
|
|
fuzzy_horns joined #rest |
| 20:32 |
|
|
graste joined #rest |
| 20:40 |
|
|
quimrstorres joined #rest |
| 21:52 |
|
|
wsiqueir joined #rest |
| 22:48 |
|
|
fuzzyhorns joined #rest |
| 23:07 |
|
|
fuzzyhorns joined #rest |
| 23:08 |
|
|
bigbluehat joined #rest |
| 23:29 |
|
|
cvander joined #rest |
