run-loop nit-picks about emberfire HOT 5 CLOSED

We handle this in fireplace with a simple event queue [1], any updates are then batched up and handled in the next run-loop. Something similar should be fairly straightforward to implement here I'd expect.

[1] https://github.com/rlivsey/fireplace/blob/master/packages/fireplace/lib/model/event_queue.js

from emberfire.

@rlivsey i notice a small comment in your code related to difficulty testing. Debounced/throttled workloads are a pain to test, I would suggest that firebase solution either disable itself for testing, or work it into the testing framework so it can be aware of the async

Also, your solution helps mitigate if a series of "synchronous" or near "synchronous" updates are pushed into ember, but this rate (depending on the app) can still be much higher then when a user can perceive. I would still suggest considering a solution (maybe configurable) that covers a larger window.

from emberfire.

Interesting. @stefanpenner, @rlivsey - what do you suggest the default interval to push changes into Ember be? We can make it configurable of course.

from emberfire.

well it makes little sense to render at more then 60fps. So (1000/16)ms would be the absolute maximum, depending on the type of application and the rate of data flowing in, I have bumped it up to as high as 50ms or 100ms. But it entirely depends on what that app dictates as an acceptable latency.

from emberfire.

See 2a6c0ec

from emberfire.