Carl Lerche
Carl Lerche
As a rule of thumb, unbounded growth is a bad idea. This is a placeholder issue to track the progress of auditing the code and bounding any growth.
Tracking questions that should probably be answered in the documentation. ### what's the general approach for resource cleanup? One cannot perform asynchronous operations in a drop function. One strategy would...
The readme should stick to the default imo.
Adds a `MultiplexConfig` struct that is used to configure how the multiplexer behaves. Remaining: * [x] Tests
Currently, there is no strategy to bubble out connection errors. However, `ClientProxy` could probably also be a future representing the connection terminating. This would allow any connection level errors to...
Unbounded is bad mmmkay, we should work on removing them.
A compilation of questions asked in Gitter / other venues #### How to perform the authentication phase (and other setup phases) of a protocol Any setup can be done during...
It would be nice to have linkerd-tcp run fully standalone and load all of the configuration settings / routing / etc.. from files.
This will require some sort of service level router.
Once we have a real case requiring grpc generic over the encoding format, then we can explore making this public. Until then, let us not be burdened by API backwards...