Thanks for the pointers! The only issue is that all code refers to node and not the browser's js… :-(
Your blocking-deref seems to rely on node/process.nextTick to essentially poll in every event-loop-cycle. Is there any node/process.nextTick equivalent that can be used in the browser? (that seems to be the only node-specific dependency as far as I can see…) Thanks, FrankS. On Nov 26, 2012, at 4:58 PM, Paul deGrandis <paul.degran...@gmail.com> wrote: > Hi Frank, > > I have a discussion about promises in CLJS using Closure's Result: > http://www.pauldee.org/blog/2012/clojurescript-and-node-js-an-experience-report/ > > Bodil is also working on the underpinnings of a proper CLJS promise > (potentially specific to Node.js): > https://github.com/bodil/redlobster > > In my talk at Clojure/Conj, I suggested using promises for upfront callbacks > (using Results), or shoving callbacks to the end of threading macros. > > I haven't personally used Closure's async/deferred stuff, but that's also a > potential option to help you focus on programming with values (instead of > wrestling with the constant callback concern). > > I hope these few tips help a little. Worst case scenario, you could wrap up > and use the Q.js promises (https://github.com/kriskowal/q) > > Regards, > Paul // OhPauleez -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
