@vodik made another good point that we should support running event loops without a background thread. The user of the loop should be able to make the decision whether or not it should be run blocking. Support for this should be carefully considered as the eventual plan is to support multi-core via asyncio loops using multiprocessing.
I propose supporting this depending on how EventLoop is run/started (say via a block kwargs).
This also drums up questions about whether separate connect() and start() methods are even needed. The original motivation was to allow for event unsubscription via unsubscribe().
@vodik made another good point that we should support running event loops without a background thread. The user of the loop should be able to make the decision whether or not it should be run blocking. Support for this should be carefully considered as the eventual plan is to support multi-core via
asyncioloops usingmultiprocessing.I propose supporting this depending on how
EventLoopis run/started (say via ablockkwargs). This also drums up questions about whether separateconnect()andstart()methods are even needed. The original motivation was to allow for event unsubscription viaunsubscribe().