Also don't use a channel unless you actually need complex coordination. I would always default to a callback first.
David On Wed, Apr 9, 2014 at 7:56 PM, David Nolen <dnolen.li...@gmail.com> wrote: > Reusable components - use callbacks > Application components (non-reusable or less re-usable) - use channels > > David > > > On Wed, Apr 9, 2014 at 7:53 PM, Brendan Stromberger < > brendanstromber...@gmail.com> wrote: > >> How can one build up the intuition to know, in what situation, whether it >> would be more beneficial to use callbacks or channels? Are there >> 'rules-of-thumb' that I could follow until that intuition is established? >> >> >> On Wednesday, April 9, 2014 8:40:19 AM UTC-7, David Nolen wrote: >> >>> It's mostly for demonstration purposes, but I think it will be a common >>> pattern when more complex coordination is required. I think components >>> should probably communicate via callbacks and applications can glue things >>> together with core.async if it's beneficial. >>> >>> David >>> >>> >>> On Wed, Apr 9, 2014 at 10:54 AM, Kendall Buchanan < >>> ken...@teachbanzai.com> wrote: >>> >>>> Hi, >>>> >>>> I have a question about Om's "Basic Tutorial", and perhaps core.async's >>>> role generally: >>>> >>>> The example given in the section, "Intercomponent Communication", uses >>>> core.async for communication between two components. Is this necessary? Or, >>>> is it demonstration? It seems in testing that I can even more easily pass >>>> functions between components as I might a channel, but without go loops? >>>> >>>> I've used React.js to some extent and obviously it lacks Clojurescripts >>>> asynchronous fanciness. Where might core.async excel in Om? >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Clojure" group. >>>> To post to this group, send email to clo...@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+u...@googlegroups.com >>>> >>>> For more options, visit this group at >>>> http://groups.google.com/group/clojure?hl=en >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "Clojure" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to clojure+u...@googlegroups.com. >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> 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 >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
