On Wed, Apr 4, 2018 at 7:38 AM, bansheee1337 via grpc.io < [email protected]> wrote:
> is it somehow supported in gRPC itself or are there any best practices to > just allow a single client connection on a gRPC server? Assuming I have a > server where multiple, especially interleaved client access doesn't make > sense, how can I prevent this from happening? I can also think of some sort > of simple self-implemented user management where the client generates a > unique ID and registers itself with the server which then blocks all other > accesses until the client deregisters again. > The answer may vary from one programming language to another, but at least in Python there is a max_concurrent_rpcs parameter available on server construction <https://grpc.io/grpc/python/grpc.html#grpc.server>. -N -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAEOYnAQ3n2p6ywZrpvAR_ViQwdvOMxqWDRP91T3tuLfP8Cp2Ng%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
