@dzannotti : The tricky part is that a single om.next query may require calls to multiple RESTful endpoints. The way I address this is to put an om-next-style "server query parser" paradoxically in the client (alongside the separate client query parser) then when I return a value from a server parser read/mutate function I return it as {:value (go ...)} which wraps any restful async call in a core.async go block. Then when a parent read/mutate function resolves its children it first "collapses" the child go blocks into the parent with a function called async-query-result:

;;Note: still alpha code
(defn async-query-result [result]
  (let [val-chan (as/chan)]
    (go (doseq [[k v] result]
          (>! val-chan [k (if (map? v)
                            (<! (:result v))
                            (<! v))]))
        (as/close! val-chan))
    (go (<! (as/reduce (fn [acc [k v]]
                         (assoc acc k v))
                       {}
                       val-chan)))))