#grpc

Do grpc clients use a connection pool?

embark: Not quite.

When you create a Channel, multiple RPCs on that Channel can use the same TCP connection.

Is there a way to create a plugin that automatically authenticates call credentials (on the server)

embark: But connection pools commonly have a method to get a cached connection to various endpoints; Channel is only for one endpoint

amlweems: Which language are you using?

Python

I've got a wrapper that adds call creds to the client

And I'm trying to find the best way to verify on the server. Currently, I'm just using a decorator on all RPC functions

amlweems: I don't know. I'm asking around.

thanks!

embark: What are you wanting to know about the connection pooling? A more specific concern I can probably answer more directly

amlweems: unfortunately you need to do that authentication yourself; I don't believe we have any hooks in gRPC Python to centralize such authentication on the server side

ejona: thanks for the help -- I'm currently processing your answer and looking back at my requirements. Just a moment

atash: do you know if there are plans to implement this?

amlweems: that doesn't bar it from being something we'll consider looking at in the future; I believe that'd be a purely additive change and up for discussion

amlweems: actually, I might have spoken too soon; gimme a minute...

amlweems: yeah, to my knowledge that's not currently there

gotcha. Is it currently planned? ;)

amlweems: not yet. We hadn't considered it yet and as it's an API change it needs at least a *little* discussion with someone who's currently on vacation.

amlweems: buuut, I'll file an issue for you to follow

atash: excellent! thanks for the help

amlweems: https://github.com/grpc/grpc/issues/5615

atash: thanks :D

amlweems: you're welcome!

ejona: actually that answered my question, thank you :)