-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Batched Reads/Writes Scheduler #345
Comments
From speaking with @tomdale and @rwjblue:
|
I want to make sure that the primitives we're building are in terms of the abstractions of the web platform. Specifically, I think we need to carefully define how Ember's scheduling semantics interact with native platform scheduling, and possibly provide APIs that let you express scheduling in terms of both. For example, I may want to schedule a task after Glimmer has inserted elements into the DOM, but before the next frame is painted. Or I may want to schedule a task right before the browser paints, without worrying about Glimmer. Can we get a document going enumerating all of the known use cases for when people use Backburner or otherwise schedule async tasks? I think this will help us define the imperative API, and also think about more declarative APIs we could use that give us more freedom to tweak in the future without breaking things. Off the top of my head, this includes things like:
|
Kicking off the idea/convo of including an API within Backburner for optimally batching work within a rAF scheduler for reads/writes. Addons obviously exist to leverage this, however it's so fundamental and a pattern we should be promoting "out-of-box" with an explicit API for doing both. Thoughts @krisselden @rwjblue @stefanpenner
The text was updated successfully, but these errors were encountered: