Not an Om user here but sounds like you are receiving messages faster than you
can handle them.
A slow consumer is a common problem in a messaging situation and core.async
has 2 built-in ways to deal with that. You can either use (async/chan
(async/slliding-buffer n)) or (async/dropping-buffer
Could you post the repo or the code where the channels are being used?
It looks like you might be putting things on a channel within the IRender
lifecycle hook which will happen once each time there is a state change.
Will
--
Note that posts from new members are moderated - please be patient
Hi William, the takes off the channel are happening in IWillMount
(posted in my original message), however, the puts onto the channel
are not happening in the React lifecycle. They are happening
separately as a result of websocket messages incoming. My puts look
like this:
(defn
Faris -- I just tried the code you mentioned and it prints 0 1 2 3 4
... as anyone would expect. I can't imagine why you are seeing 0 3 7
10 as there is surely more going on there on your side, because that
is not what should be happening.
On Fri, Jul 18, 2014 at 10:16 AM, Faris Nasution
Yep that was a mistake on my part, actually the code isn't exactly like
that. I wrap the (chan) inside a function and then in go-loop I invoke that
function.
On 18 July 2014 10:37, Andrew Stoeckley andrew...@gmail.com wrote:
Faris -- I just tried the code you mentioned and it prints 0 1 2 3 4
