Run callback in a new thread about pymesos HOT 3 CLOSED

I think it is better to let user decide whether to run a particular callback synchronously or asynchronously.
If you decide to run it asynchronously, you can use thead, threadpool, coroutine or anything you like to run it. pymesos neither have the knowledge of the user's need, nor is able to force user to use any kind of these solutions.

And assume, we are now callback in another thread, for example _io_thread. we would also be blocked infinitely, because statusUpdate cannot be called in _io_thread as it is occupied by reconcile_all_running_tasks.

If you aware that the old pymesos (<0.2.0) is using two threads instead of one, the main concern is we should not make IO lagged by slow callback. it is not for blocking issue. In this new version, we decide to simplify our design for better maintainability. and we see 20% performance boost in our production environment. I think it is worthy.

Hope my explanation is helpful.
thx

from pymesos.

you are right, running all callback in a new thread can't solve this problem, but this is a trap to the user of this package. this package needs documentation. anyway thx

from pymesos.

yes, documentation is needed badly.
we will see whether we can spare some time to document this.
thank you for your support during this long time.

from pymesos.