Thanks for the clarification, that helps a lot. And I agree you wouldn't
expose channels in the public API for a component, that's definitely an
implementation detail.
I have more ideas/questions on the topic, but I don't want to hijack this
thread, and I probably need to spend some more
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
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
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
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
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) -
David,
This seems to be a different take on things than you proposed in your
series of CSP articles last summer. I'm not saying that is a bad thing -
if an idea doesn't pan out, it needs to be scrapped (and most of us cling
to bad ideas longer than we should). I'm just curious why the change
I would probably still do an async autocompleter component with channels
where it seems useful *internally*. I just wouldn't expose channels as an
interface to users of this component. I think most of points from my CSP
posts still hold even with React/Om.
David
On Wed, Apr 9, 2014 at 11:57 PM,
