improves transport api and lifecycle #178
Merged
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.
NOTE: Depends on #177
CoroutineScopewhere to launchServerin general way for all transports: in that way, users and transports can control both life-cycle and dispatchers for server running codeCoroutineContexttoClientTransportto specify in which context handling will happenClientTransportto some JobConnectionandRSocketnow implementsCoroutineScopeLimiterto work all time even if not efficient (@OlegDokuka will improve this)SelectorManagerbased on provided context: default dispatcher for JVM is IO, if you override it, make sure, that this dispatcher is suitable for blocking tasks, don't useDefaultdispatcher, for TCP