Add new implementation of RunnableScheduler which stops the thread on destroy #35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anubhav7nov
reviewed
Aug 2, 2022
| @Volatile | ||
| private var globalListener: MessageListener? = null | ||
|
|
||
| @Volatile | ||
| private var isInitialised = false | ||
| private val isInitialised = AtomicBoolean(false) |
deepanshu42
force-pushed
the
task/courier
branch
from
3fcceae to
63d2827
Compare
deepanshu42
force-pushed
the
task/courier
branch
from
63d2827 to
cd0624d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#31 Create a new implementation of
IRunnableSchedulerwhich stops the thread when destroy api ofMqttClientis invoked. The thread is started again when connect api is invoked.To use this new implementation, pass the config
isRunnableSchedulerV2Enabledas true insideExperimentConfigs