OK thanks. We will work around it in the application layer.
On Mon, Dec 5, 2016 at 5:54 PM Qi Zhao wrote:
> On Mon, Dec 5, 2016 at 5:35 PM, Arya Asemanfar <
> arya.aseman...@mixpanel.com> wrote:
>
> Since a TCP load balancer is only aware of TCP packets and not HTTP2
&
main knowledge and just make a synthetic example. :)
>
> Actually I think you can simply Dial a ClientConn and Close it when some
> timer fires in order to mimic MaxConnectionLifetime you proposed regardless.
>
> On Mon, Dec 5, 2016 at 3:07 PM, Arya Asemanfar <
> arya.aseman...@mi
grpc servers?
>
> On Mon, Dec 5, 2016 at 2:49 PM, Arya Asemanfar <
> arya.aseman...@mixpanel.com> wrote:
>
> Sorry, I meant grpc server. Yes you are right if the TCP load balancer
> restarts there is no problem, so my scenario only applies if the grpc
> server restarts.
>
Sorry, I meant grpc server. Yes you are right if the TCP load balancer
restarts there is no problem, so my scenario only applies if the grpc
server restarts.
On Mon, Dec 5, 2016 at 2:17 PM Qi Zhao wrote:
> On Mon, Dec 5, 2016 at 12:13 PM, Arya Asemanfar <
> arya.aseman...@mixpanel.c
ks for the info. My comments are inline.
>
> On Sun, Dec 4, 2016 at 7:27 PM, Arya Asemanfar <
> arya.aseman...@mixpanel.com> wrote:
>
>> Hey all,
>>
>> We're considering implementing some patches to the golang grpc
>> implementation. These are things we thin
Hey all,
We're considering implementing some patches to the golang grpc
implementation. These are things we think would better fit inside of grpc
rather than trying to achieve from outside. Before we go through the
effort, we'd like to gauge whether these features would be welcome
(assuming we
