2017-02-01 20:26:09 +0000metteko__(~mettekou@gateway/vpn/privateinternetaccess/mettekou)
2017-02-01 20:26:48 +0000mettekou_(~mettekou@109.140.170.223) (Read error: Connection reset by peer)
2017-02-01 21:13:38 +0000metteko__(~mettekou@gateway/vpn/privateinternetaccess/mettekou) (Quit: metteko__)
2017-02-01 21:50:18 +0000stepcut(~stepcut@c-73-22-171-228.hsd1.il.comcast.net)
2017-02-01 21:55:22 +0000 <jkarni> fuzzyhorns: re: HATEOAS
2017-02-01 21:56:05 +0000 <jkarni> fuzzyhorns: the idea is that, since we have the entire definition of the API, we should be able to fulfill OPTIONS requests (and the like) automatically
2017-02-01 21:56:19 +0000 <fuzzyhorns> jkarni: what do you mean options requests?
2017-02-01 21:56:44 +0000 <jkarni> http://zacstewart.com/2012/04/14/http-options-method.html
2017-02-01 21:57:15 +0000 <fuzzyhorns> ah yes, ive heard of this in theory but never seen an api support it
2017-02-01 21:57:28 +0000 <jkarni> fair enough
2017-02-01 21:57:29 +0000 <fuzzyhorns> and jkarni that is something i want to work on
2017-02-01 21:57:49 +0000 <jkarni> more common is for e.g. GET requests to be wrapped in something that links to other relevant endpoints
2017-02-01 21:57:56 +0000 <jkarni> e.g. http://restcookbook.com/Basics/hateoas/
2017-02-01 21:58:04 +0000 <fuzzyhorns> i know what hateoas is :)
2017-02-01 21:58:09 +0000 <jkarni> but the implementation would be very similar
2017-02-01 21:58:11 +0000 <jkarni> sorry :)
2017-02-01 21:58:30 +0000 <fuzzyhorns> http://amundsen.com/hypermedia/hfactor/
2017-02-01 21:58:36 +0000 <fuzzyhorns> this is what i'm interested in
2017-02-01 21:58:56 +0000 <fuzzyhorns> no worries, i wasnt offended, just didnt want to derail down a deeper definition of it
2017-02-01 21:59:27 +0000 <fuzzyhorns> & https://rawgit.com/inadarei/draft-prefer-transclude/master/draft-inadarei-prefer-transclude-xml-01…
2017-02-01 22:00:59 +0000 <jkarni> cool
2017-02-01 22:01:53 +0000 <jkarni> there's a little bit of difficulty with "rel" (can't easily be done automatically)
2017-02-01 22:02:21 +0000 <jkarni> but the idea I came up with for the implementation would be:
2017-02-01 22:02:45 +0000 <jkarni> assume the API structure indicates relevance
2017-02-01 22:02:48 +0000 <jkarni> i.e.
2017-02-01 22:03:04 +0000 <jkarni> ifendpoints have the same path, but different methods, they're related
2017-02-01 22:03:16 +0000cpennington(~cpenningt@18.176.7.247) (Remote host closed the connection)
2017-02-01 22:03:42 +0000 <fuzzyhorns> oh you see rel as just "related"?
2017-02-01 22:03:57 +0000 <jkarni> yeah, though "rel" specifies the specific relation
2017-02-01 22:04:04 +0000 <fuzzyhorns> i tend to think of it as just a sort of abstraction of the binding
2017-02-01 22:04:34 +0000 <fuzzyhorns> like rather than "/some/arbitary/url/about/v1/1" i hide the url underneath link_relation="about"
2017-02-01 22:05:13 +0000 <jkarni> moreover, if an endpoint is a parent of another (matches up to the previous '/'), then they're also related, arguably by the relationship with the name of the suffix path
2017-02-01 22:05:27 +0000 <jkarni> what do you mean exactly?
2017-02-01 22:06:08 +0000 <fuzzyhorns> http://nordicapis.com/designing-a-true-rest-state-machine/
2017-02-01 22:06:31 +0000 <fuzzyhorns> if you go down to "Example State Machine: IoT Toaster"