portkey

Portkey: from REPL to Serverless in one call
baptiste-from-paris 2018-05-22T06:20:05.000279Z

I don’t understand the need for req and resp, their responsability

cgrand 2018-05-22T09:00:46.000174Z

specs don’t transform ser (resp. deser) transforms to (resp. from) conforming value (eg take care of lifting collapsed lists from HAL) — these transformations are local req takes whatever ser on the root shape produced and creates a request (it may imply moving things around, out of the body to a header oa a query param) — these transformations are global resp is the mirror of req: it takes a response, cobbles every piece of value together in a single value to pass to deser

cgrand 2018-05-22T09:01:35.000379Z

resp -> deser+ -> conform conform -> ser+ -> req

cgrand 2018-05-22T09:40:05.000130Z

the + denotes recursive call (non standard notation, yeah!)

baptiste-from-paris 2018-05-22T10:53:36.000396Z

I understand that ser is local but req is only protocol dependent, why creating req-* forr every input ?

baptiste-from-paris 2018-05-22T10:57:27.000203Z

I am feeling dumb ^^

viesti 2018-05-22T13:28:54.000513Z

that is a recurring feeling for me too, generally

viesti 2018-05-22T13:30:54.000579Z

relates to grasshopping, I think

cgrand 2018-05-22T14:30:59.000196Z

(map #(str "ser-" %) inputs) vs (map #(str "req<-" %) input-roots) One ser per shape used as (part of) input but only req<- for root input shapes (aka messages)

viesti 2018-05-22T15:07:57.000948Z

😄

baptiste-from-paris 2018-05-22T20:05:38.000534Z

Ok, I’ll digest that tomorrow and try to do a POC this week