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.

Sign up for GitHub

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

Jump to bottom

Define an execution model #15

Open

mehcode opened this issue Mar 22, 2017 · 1 comment

Labels

Owner

mehcode commented Mar 22, 2017

Currently jobs are run manually (with a helper method to run all currently pending jobs). We should define an execution model.

Does it make sense to have more than one execution model (sync vs async)?
How does the API look?

my_agenda.start()

How does the agenda, itself, execute (in a thread or coordinated with an event loop)?
How does each job execute (threadpool) ?

mehcode added enhancement question and removed enhancement labels

mehcode mentioned this issue

Thread-pool Dispatch of Jobs #6

Closed

Boscop commented Oct 23, 2017

Are Jobs re-entrant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment