Ok, so I'm new to websockets ( as well as clojure ). New enough to possibly be asking a very stupid question. But how are people using them? Do I open one and put everything I want in it within a map ?

@timfield: We’re using Sente which provides some higher level abstractions over websockets

But you can just send maps over the wire. You probably want to serialise it with something, either EDN or Transit are good options

Ok I'm using Chord currently

And I think I'm going to send a single map that represents the whole page state

Sure

Ok, so I'm not doing anything really odd then. Good to know

What’s the context behind sending a map with the page state?

Is that everything that the page needs to render itself?

yeah

What else are you using on the frontend? Reagent/Om?

Yeah quiescent

another React wrapper

What I don't like about this idea tho, is that I'm making a few API requests to construct the page state, and if they are in a single map, then I need to wait for all my API requests to return with data before I can begin rendering

If I was doing this with ajax, each component might fetch its own state via ajax

but I'm not sure how to do that with websockets

Context, Clojure on server is creating page state, sending page state via a websocket to ClojureScript

Agh, but what if those API requests wrote to the channel when ready, then my client listens to that channel and reacts based on its content

Have you looked at re-frame? It’s one way to do what you’re describing

re-frame looks rad. Next project for sure. For now I'm rolling with this setup; Single channel & single page state map. Both are passed down to quiescent components which can use the channel to trigger a change to the single page state map ( on the server ) which is then passed down again.

Sounds like flux, which I like.

Ideal pulled from http://www.parens-of-the-dead.com/