This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-09
Channels
- # announcements (1)
- # atlanta-clojurians (1)
- # beginners (198)
- # calva (4)
- # cider (16)
- # clara (8)
- # cljs-dev (14)
- # cljsrn (4)
- # clojure (204)
- # clojure-europe (3)
- # clojure-gamedev (2)
- # clojure-italy (8)
- # clojure-nl (17)
- # clojure-poland (3)
- # clojure-russia (20)
- # clojure-spec (32)
- # clojure-uk (45)
- # clojurescript (59)
- # community-development (1)
- # core-async (25)
- # cursive (20)
- # datomic (47)
- # emacs (7)
- # fulcro (8)
- # iot (1)
- # iotivity (2)
- # jobs (1)
- # jobs-discuss (8)
- # juxt (11)
- # luminus (5)
- # nrepl (4)
- # off-topic (136)
- # onyx (24)
- # other-lisps (1)
- # parinfer (74)
- # pedestal (1)
- # planck (3)
- # portkey (67)
- # random (1)
- # re-frame (28)
- # reagent (11)
- # reitit (9)
- # remote-jobs (3)
- # ring-swagger (2)
- # rum (3)
- # shadow-cljs (96)
- # slack-help (3)
- # spacemacs (6)
- # tools-deps (3)
- # unrepl (1)
- # vim (4)
Hello friends, so I finished to implement all protocol for making requests
I had some tests checking body generation
Would be great to check headers and URI in the near futur
I propose to create merge it in the official repo on a branch.
It lacks deserialization yet, I have to think about it, if anyone has ideas
hmh, somehow loosing ability to concentrate on reading blog posts. I realized that I only skimmed Matthew's post, and he demonstrated Application CDS too (creating memory mapped archive of user classes)
I have faint memory that class data sharing originated from the jdk build that Apple used to maintain but I might be way off (idea was to lower memory use by sharing read only memory mapped base classes, similar to what native libraries might do)
(case protocol
"rest-xml" (params-to-body-rest-xml req)
"ec2" (params-to-body-ec2 req)
"query" (params-to-body-query req)
"rest-json" (params-to-body-rest-json req)
"json" (params-to-body-json req)))
neat :) doing deser right now
it’s going well for json/rest-json
offcourse xml is a pain in the ass
and I have to put back documentation done by Mr Kimmo himself 😉
I’d really love to see some cljs working some day
and the ser/deser design rely on pure datastructure
which mean it’s possible there is nothing to touch in sdk itself
only signing and request
http calls
@viesti, I think ou tried the cognitect one, what do you find better / worst ?
yep, but I did not tried it
they don't gen functions, rely on "data centric" callsite, (aws/invoke s3-client {:op :ListBuckets})
which is better or kind if the same
like spec exercise
anyway my point was also to finish an OSS of a big size
if nobody use it, it’s fine 😄
but at least it will be truly open-source 😋
haven't really yet read on SubtrateVM nor Graal, but this sounds eerily close to portkey abstract interpretation: https://github.com/oracle/graal/blob/master/substratevm/REFLECTION.md
what’s your idea behind all this ?
maybe nothing useful, just that the bytecode analysis in portkey could be used for generating a list of classes for the native-image tool in subtrate/graal
could make native image bulding easier, if in the repl, one could provide entry point function and the pass classes resolved from that point onto native image packager
I did not look much at all the serverless stuff recently
seems a lot is happening
which means you can create aws for your own language right ?
but in aws, one can now have a custom runtime for any language. You poll events from a local http api, and push back reponses. The runtime just invokes your binary.
and one can share runtimes via layers, Ghadi haa done this https://github.com/ghadishayban/lambdaclj-jdk11
good night
xml -> formatted map
this was not fun 😄