-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: unstable dynamic routing feature #599
feat: unstable dynamic routing feature #599
Conversation
use thiserror::Error; | ||
use tokio::{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@adamspofford-dfinity even though futures_util
can run with tokio
runtime, i'm not sure the performance will be as good as with pure tokio
. As tokio
specific utilities like tasks are optimized for tokio
, so i'm a bit concerned with the decision to remove it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i get the rationale to make the code work for wasm
builds too, but don't like that standard build
will potentially loose in performance
The final design of dynamic routing in the agent is not complete and other teams want to be already using it, so this merges the original design with the minimum number of changes to support WASM, and exports it under the feature
_internal_dynamic-routing
. Work on the final design will continue in the background.