This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-06
Channels
- # admin-announcements (1)
- # announcements (32)
- # babashka (38)
- # beginners (91)
- # braveandtrue (1)
- # calva (1)
- # cider (9)
- # cljsrn (19)
- # clojure (129)
- # clojure-bay-area (3)
- # clojure-europe (24)
- # clojure-italy (1)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-spec (10)
- # clojure-uk (24)
- # clojurescript (14)
- # community-development (7)
- # conjure (16)
- # cursive (3)
- # datomic (20)
- # defnpodcast (4)
- # emacs (11)
- # figwheel (2)
- # fulcro (5)
- # helix (6)
- # integrant (3)
- # jackdaw (5)
- # java (6)
- # jobs (1)
- # kaocha (13)
- # lsp (8)
- # malli (29)
- # meander (2)
- # off-topic (120)
- # pathom (3)
- # podcasts-discuss (6)
- # portal (6)
- # re-frame (27)
- # reagent (5)
- # releases (4)
- # remote-jobs (6)
- # rewrite-clj (9)
- # shadow-cljs (108)
- # xtdb (5)
how are folks automatically signing out clients if their session is invalidated server side? I’ve been following the auth example in RAD to check the session, which will check the session once on pageload, (via the UISM auth-machine), but what if halfway through using the app, the redis session store is invalided? My pathom queries / mutations will stop returning results for data that requires proper authorization, but this can look like data loss to the clients.
perhaps checking the session in ring middleware, and utilizing custom response-middleware
in the client?
yeah, that sounds like the right kind of move. also could do a pathom plugin: https://blog.wsscode.com/pathom/v2/pathom/2.2.0/plugins.html