Rei Shimizu

/test all

> I had a discussion with @wu-sheng offline, and my idea is just "having multiple streams and rotate/drain one stream periodically at a time" rather than "use/reconnect one stream and...

ok. We may have any points that we need further discussion, but I can take this task.

To sum up the opinions The current implementation policy (multiplexing connections in a pool and RR messages) is redundant. Therefore, it should be changed to work as follows. Set the...

> For connection re-establishment isn't whatever LB policy is in effect OK? RR, LR, etc? It will be affected with `max_stream_duration` but part of my requirement is done with this...

> I think that could be an optional feature on the connection pool. I think this feature is similar to retry, so we may reuse retry logic after introducing a...

Sure. It will be treat as enhancement but no feature for `0.1.0`. Thanks.

@kezhenxu94 Sounds good. But I'm not sure how to fail build on MacOS. Could you provide logs?

It won't be a problem on Envoy integration so I ignored this problem although I already know about it. But when we use it as SDK, It will be a...

@liberize After all we don't have to allow sharing tracer between threads because it should be lock-free. Have you considered this to have per thread?