Renjie Cai

@gszpura Of course, that is exactly what i'm going to do As for the timeline, since I thought it's not a urgent feature, currently i'm working on a demo app...

@stupidchen you can just write your thoughts about this feature under this issue I have some ideas about this feature: Add a `EnpointManager` to control which endpoint should the client...

That might be the solution. But I'll have to dig into it to find the cause. Actually the "swagger cache" was just a temporary solution. My goal is to auto...

like Client and AioClient. I planned to add asyncio support to current stateful utils

yeah, that's true I think I can change the module name to etcd3-py by the version 1.0.0

> ref: https://github.com/tensorflow/serving/issues/1382#issuecomment-503375968 Since this lib is using grpc-gateway to make request, It's not likely able to set the grpc option. But maybe you can paginate by using the `key`...

Yeah, maybe we can add a new stateful util, named like "ranger util" Thank you so much for contribution.

I prefer adding a new stateful util. Cause you have to make multiple request in during the process which means you must have **states** to tell what page you are...

I was planning to write some higher level apis too, like get, get_prefix, delete_prefix, get_keys. You can, if you like, just stick to writing a function and put them in...

yeah, it's impossible to make a function both sync and async while it makes multiple requests brefore return. so i prefer to write two stateful util (async and sync) and...