These are chat archives for jdubray/sam

25th
Nov 2017
Victor Noël
@victornoel
Nov 25 2017 10:50
A followup on the discussion of APIs : https://mmikowski.github.io/the_lie/ (found this while looking for alternatives to REST APIs). JSON-RPC seems also an interesting approach
Victor Noël
@victornoel
Nov 25 2017 10:59
only thing I like with REST is that I can take advantage of browser caching with cache control headers and not bother to manage that at the application level
Paolo Furini
@pfurini
Nov 25 2017 11:46
Json-rpc could be used for the command/action interaction
Victor Noël
@victornoel
Nov 25 2017 11:51
the "problem" of jsonrpc is that it is using one endpoint, so you loose the advantages of http such as cache control, but apart from that, I wonder sometimes if I shouldn't be using that instead of a complex jetty/(spark|jersey|etc)/jackson setup with all the wiring done by hand...
Paolo Furini
@pfurini
Nov 25 2017 12:58
Should be used for post request, in general non idempotent ones, where caching is not desirable
I generally divide commands/actions requests from query/select ones. The latter benefit from changing
Nick Maravich
@nick_maravich_twitter
Nov 25 2017 13:38
@jdubray Wow! That's impressive - almost 4 decades of coding. I was a BA cleaning excel data late one evening at work when a developer asked me what I was doing. He looked over my shoulder and said "let the computer be the monkey" and showed me a Macro. That was the start of it all for me :) Thank you. You addressed my question and I will certainly check out PouchDB.
Victor Noël
@victornoel
Nov 25 2017 13:45
@pfurini ah ok, I got your point. Yes, then using jsonrpc for commands and a rest-like api for queries sounds good!