This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-30
Channels
- # aleph (4)
- # announcements (5)
- # architecture (1)
- # aws (5)
- # babashka (12)
- # beginners (143)
- # chlorine-clover (4)
- # cider (16)
- # clj-kondo (44)
- # cljfx (26)
- # cljsrn (2)
- # clojure (34)
- # clojure-europe (28)
- # clojure-gamedev (1)
- # clojure-nl (3)
- # clojure-provo (2)
- # clojure-spec (6)
- # clojure-uk (17)
- # clojurescript (99)
- # code-reviews (6)
- # core-async (15)
- # cryogen (9)
- # cursive (14)
- # data-science (1)
- # datomic (16)
- # duct (1)
- # events (4)
- # exercism (1)
- # figwheel-main (3)
- # fulcro (3)
- # hugsql (7)
- # leiningen (4)
- # malli (15)
- # off-topic (13)
- # pathom (8)
- # re-frame (7)
- # reitit (35)
- # remote-jobs (1)
- # sci (10)
- # shadow-cljs (32)
- # sql (5)
- # tools-deps (102)
- # tree-sitter (3)
- # uncomplicate (7)
- # vim (40)
- # xtdb (8)
@jjttjj Do you want to save it as a gist for a longer-lasting record than Clojurians Slack? I'm not too familiar with the WS side of Aleph yet, but I'll want to do something very similar (feed a stream to a WS with start/stop capabilities) in the next couple weeks. If you're not in a hurry, I can give a better review then.
(Minor typo: alep.http
should be aleph.http
, I assume)
@kingmob Sure, it's changed considerably since I sent that one, here's what I'm currently working with. Now it just returns a stream on which is put each new connection duplex stream upon being connected. I just changed it a bunch this morning and there might still be a bug or two https://gist.github.com/jjttjj/0dc1fbe001578f5580fedfad8ed81a80
Cool, will check out.