Skip to content
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

Scheduling #10

Closed
zebulonj opened this issue Jul 6, 2015 · 0 comments
Closed

Scheduling #10

zebulonj opened this issue Jul 6, 2015 · 0 comments

Comments

@zebulonj
Copy link
Owner

zebulonj commented Jul 6, 2015

I want to be explicit about how dispatched signals are scheduled for processing. This is particularly important in the context of cascading signals, where a secondary signal is generated from within an action (triggered by a prior signal).

In the case of secondary signals, processing should be queued for after completion of the current and any pending signals.

In the case of primary signals (triggered by user action), I'm less certain but inclined to give the same treatment.

This should (a) allow easier reasoning about the timing of actions and (b) improve performance by breaking up otherwise long running processes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant