expose some structs to be able to use a non-tokio executor #296
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.
For Inox(https://github.com/vhdirk/inox/) I'm combing tarpc with the glib executor as opposed to the default tokio executor.
In order to also have deadlines for requests, I needed to fork
ClientHandler
in my own project. That requires some changes in tarpc so I can create, for instance, a response struct. See https://github.com/vhdirk/inox/blob/master/inox-gtk/src/webextension/rpc.rsI'm still working on the client side. That one is harder since tokio's
TimeOut
s are not compatible with custom executors, but they are used throughout the (generated) client code.