This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-27
Channels
- # aws-lambda (3)
- # beginners (3)
- # boot (327)
- # capetown (2)
- # cider (156)
- # cljs-dev (368)
- # cljsjs (13)
- # cljsrn (53)
- # clojure (403)
- # clojure-czech (5)
- # clojure-dev (4)
- # clojure-greece (2)
- # clojure-russia (72)
- # clojure-spec (12)
- # clojure-uk (129)
- # clojurescript (156)
- # core-async (1)
- # cursive (33)
- # datomic (35)
- # emacs (10)
- # events (1)
- # hoplon (4)
- # jobs-discuss (3)
- # klipse (1)
- # lein-figwheel (14)
- # leiningen (5)
- # luminus (5)
- # off-topic (15)
- # om (69)
- # om-next (2)
- # onyx (2)
- # parinfer (15)
- # perun (12)
- # re-frame (30)
- # reagent (7)
- # ring-swagger (8)
- # spacemacs (10)
- # specter (6)
- # untangled (69)
- # yada (13)
how would you manage a datomic database value in your resources? Let's say you need the db value in multiple interceptors (auth, properties, response). You probably want to insert an interceptor that updates the context before all that stuff happens?
We establish the database value and assoc into the req context, using an interceptor precise because its used in auth. @stijn
makes sense. in our case we do auth with an external system, so assoc'ing it in properties is fine
If you want to know more about this interceptor, it's discussed in my blog article today: https://juxt.pro/blog/posts/live-programming-websites.html
Retweets welcome!
integrant's suspend / resume
functionality got me thinking on the same line, where you can update e.g. your handler without restarting the webserver
one concern is, how can you guarantee everything still works when your server fails, the node dies, or becomes unusable and you have to restart everything from scratch?
I saw that. Really want to look at James's new stuff