You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I spent a little time talking with @trxcllnt yesterday about scheduler design. I've also glossed over this briefly with @jhusain and @benjchristensen
I have a REALLY, REALLY primitive impl in the codebase now, but it needs work. In particular it needs a better design.
Right now it's a global scheduler. But you'll notice I added a dispose() method to it. This is because I initially created it as a class, and thought scheduling might be instance based. This would make scheduling more flexible. However, global scheduling is very useful for things like Framework lifecycles (@IgorMinar, @machty).
I'm looking for input as to how to make this flexible but easy to understand for authors.
The text was updated successfully, but these errors were encountered:
... and I do realize the primitive scheduler I've put in place is an "execute until done" sort of scheduler. Meaning it doesn't provide gaps for other code execution. This is a bare-metal simplistic impl. I think for most browser-based use cases, adding gaps ala MicroTask scheduling probably isn't completely necessary because the event stream sources themselves will be async, but there's definitely a need for that type of scheduler.
I spent a little time talking with @trxcllnt yesterday about scheduler design. I've also glossed over this briefly with @jhusain and @benjchristensen
I have a REALLY, REALLY primitive impl in the codebase now, but it needs work. In particular it needs a better design.
Right now it's a global scheduler. But you'll notice I added a dispose() method to it. This is because I initially created it as a class, and thought scheduling might be instance based. This would make scheduling more flexible. However, global scheduling is very useful for things like Framework lifecycles (@IgorMinar, @machty).
I'm looking for input as to how to make this flexible but easy to understand for authors.
The text was updated successfully, but these errors were encountered: