Fork me on GitHub

yeah, that seems to make sense - it's a bit of an unfamiliar use-case for me - we have precisely 1 duplex stream in our whole (decent sized - 238 namespaces require codebase, and that, like yours, is the websocket stream. most of our stream ops are data-transformations


there is also the xform based stream constructor you could use - (s/stream 0 (map ->json)) although you'd have to use a s/connect too, so i'm not sure that's any more succinct than s/connect-via