rust: Improve service handler wrappers #249
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.
Borrow some good ideas for wrapping callbacks from @eloff's asset handler work in #229.
In particular, I love the idea of handling the
tokio::spawn
andtokio::task::spawn_blocking
on our side, because it handles the 99% case beautifully. Folks that want even finer control can always implementHandler
themselves.Changes here:
handler_fn
(which took(Request, Responder)
as arguments).sync_handler_fn
ashandler_fn
.blocking_handler_fn
andasync_handler_fn
for blocking and async function handlers.'static
bounds.