Follow up on:
The PR introduced the WorkerChannel abstraction for decoupling gRPC from the project's core logic. This way people can bring their own transport protocols.
The WorkerChannel is still coupled to http::HeadersThough mainly for two reasons:
- Transporting a serialized version of the
ConfigOptions injected by the user
- Passing through headers across worker jumps
This probably should be factored out of the core logic of this project into the gRPC specific implementation, or maybe some other module that more implementations can use, not just gRPC.
Before anyone taking this issue, please feel free to post the approach here, as I'd expect this to need some discussion.
Follow up on:
The PR introduced the
WorkerChannelabstraction for decoupling gRPC from the project's core logic. This way people can bring their own transport protocols.The
WorkerChannelis still coupled tohttp::HeadersThoughmainly for two reasons:ConfigOptions injected by the userThis probably should be factored out of the core logic of this project into the gRPC specific implementation, or maybe some other module that more implementations can use, not just gRPC.
Before anyone taking this issue, please feel free to post the approach here, as I'd expect this to need some discussion.