This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-28
Channels
- # aleph (4)
- # announcements (5)
- # babashka (28)
- # babashka-sci-dev (13)
- # beginners (63)
- # calva (76)
- # cider (113)
- # clara (7)
- # clj-kondo (42)
- # cljdoc (1)
- # clojure (170)
- # clojure-europe (20)
- # clojure-nl (17)
- # clojure-norway (3)
- # clojure-spec (12)
- # clojure-sweden (1)
- # clojure-uk (6)
- # clojurescript (55)
- # clojureverse-ops (1)
- # consulting (1)
- # core-async (9)
- # cursive (16)
- # data-science (1)
- # datascript (8)
- # datomic (27)
- # emacs (14)
- # events (1)
- # fulcro (10)
- # graphql (9)
- # gratitude (1)
- # jobs (6)
- # jobs-discuss (5)
- # leiningen (10)
- # lsp (35)
- # missionary (4)
- # nextjournal (9)
- # off-topic (46)
- # pathom (15)
- # pedestal (5)
- # polylith (37)
- # portal (15)
- # re-frame (22)
- # reagent (4)
- # reitit (5)
- # reveal (18)
- # shadow-cljs (20)
- # tools-deps (7)
- # xtdb (10)
hi there, I'm trying to do a fairly basic demo of some SSE with pedestal. I think I'm missing something obvious. I've tried the demo here: http://pedestal.io/reference/server-sent-events and it "works" in that I see the events in the client. But in order to make that happen I need to close the event-chan
which doesn't really make sense to me? I was hoping to keep the event-chan as a long running pipe for events which would get picked up on the client.
I need a way to "flush" the channel to the client without closing the chan
or maybe I'm doing something dim on the client to cause that ?
well I've spent some time looking at the client side and I don't think it's that
Are you running this demo: https://github.com/pedestal/pedestal/tree/master/samples/server-sent-events? You are indeed supposed to be able to keep the event-channel open for as long as you need it. When using SSE a separate dispatch loop starts piping from the event-channel to the client, so something strange is going on if you need to close the event-channel for this to happen.