CrossClj

0.3.3 docs

SourceDocs



RECENT

    untangled-websockets

    Clojars

    Mar 16, 2017


    Readme

    Index of all namespaces


    The README below is fetched from the published project artifact. Some relative links may be broken.

    Untangled Websockets

    A set of helpers to use websockets with your untangled applications.

    Sente is used to define the websocket layer.

    Clojars Project

    Usage

    Server

    There are two protocols on the server side:

    (defprotocol WSNet
      (add-listener [this ^WSListener listener]
        "Add a `WSListen` listener")
      (remove-listener [this ^WSListener listener]
        "Remove a `WSListen` listener")
      (push [this cid verb edn]
        "Push from server"))
    
    (defprotocol WSListener
      (client-added [this ws-net cid]
        "Listener for dealing with client added events.")
      (client-dropped [this ws-net cid]
        "listener for dealing with client dropped events."))
    

    WSNet is implemented by the ChannelServer.

    WSListener is for you to implement. It allows for listening to client added and dropped (closed) actions. An example might look like this.

    (require '[untangled.websockets.components.channel-server :as cs])
    (require '[app.api :as api]) ;; see below.
    
    (defrecord ChannelListener [channel-server]
      cs/WSListener
      (client-dropped [this ws-net cid]
        (remove-user-to-db cid)
        (api/notify-others ws-net cid :user/left {:user cid}))
      (client-added [this ws-net cid]
        (add-user cid)
        (api/notify-others ws-net cid :user/entered {:user cid}))
    
      component/Lifecycle
      (start [component]
        (cs/add-listener channel-server component)
        component))
      (stop [component]
        (cs/remove-listener channel-server component)
        component))
    
    (defn make-channel-listener []
      (component/using
        (map->ChannelWrapper {})
        [:channel-server]))
    

    Hooking untanlged websockets into the system is simple. We will add the ChannelServer component and the ChannelListener component from above, and then define the route:

    (require '[untangled.websockets.components.channel-server :as cs])
    
    (defn make-system []
      (core/make-untangled-server
        :config-path "config/app.edn"
        :parser (om/parser {:read logging-query :mutate logging-mutate})
        :parser-injections #{}
        :components {:channel-server  (cs/make-channel-server)
                     :channel-wrapper (make-channel-listener)}
        :extra-routes {:routes   ["" {["/chsk"] :web-socket}]
                       :handlers {:web-socket cs/route-handlers}}))
    

    The listing for :extra-routes is the endpoint for your websocket. route-handlers is defined in untangled.websockets.components.channel-server. This will leave the default “/api” route in tact in case you need to use if for other clients/reasons.

    In your api you may add something like this:

    (require '[untangled.websockets.protocols :refer [push]])
    
    (defn notify-others [ws-net cid verb edn]
      (let [clients (:any @(:connected-uids ws-net))]
        (doall (map (fn [id]
                      (push ws-net id verb edn)) ;; Use the push protocol function on the ws-net to send to clients.
                    (disj clients cid)))))
    
    (defmulti apimutate om/dispatch)
    
    (defmethod apimutate 'datum/add [{:keys [ws-net cid] :as env} _ params] ;; ws-net is the protocol defined in untangled-websockets and it is added to the environment for use by mutations and components.
      {:action (fn []
                 (swap! db update :data conj params)
                 (notify-others ws-net cid :app/data-update params) ;; Push to topic with data (params) excluding cid
                 {})})
    

    Client

    In the client we need to override the default networking:

    (defonce app (atom (uc/new-untangled-client
                         :networking (wn/make-channel-client "/chsk" :global-error-callback (constantly nil))
                         :initial-state initial-state
                         :started-callback (fn [{:keys [reconciler]}]
                                             ;; You may want to put some code here to run on startup.
                                             ))))
    

    We override the default network with our own implementation of a network. We hook the client up to use “/chsk” as the route for communicating with the server, and we give a callback for global errors.

    We will also need to extend the untangled.websockets.networking/push-received multimethods, for handling pushed messages.

    (require '[untangled.websockets.networking :as un])
    
    (defmethod un/push-received :app/data-update [{:keys [reconciler] :as app} {:keys [topic msg] :as message}] ;; message => {:topic verb :msg edn}
      (om/transact! reconciler `[(do.with/data {:data msg}) :data]))
    

    Note that you have access to the reconciler (for that matter the entire app) here. You can call (om.next/merge! reconciler ...) or (om.next/transact! reconciler ...) alternatively. That part is up to you.

    Check out the Untangled Cookbook for an example usage. Feel free to ping the untangled on clojurians slack for help.

    License

    Copyright © 2016 NAVIS

    Distributed under the MIT License.