On Tue, Aug 9, 2016 at 5:42 PM, Shraddha Thakkar <[email protected]> wrote:
> I am implementing a gRPC server and client in python. My requirement is > that the server continuously streams the system data to the client once the > client establishes a connection, so I have implemented a server streaming > (response streaming ) RPC call for this requirement. > The remaining RPC Calls need to work in parallel and so I have initiated a > new thread on the client end just to receive the stream of data and the > main thread executes the remaining RPC Calls required. > This all sounds good so far... But I observe the output to be gibberish so it seems I need to handle > multiple simultaneous client requests on the server side, using tread pool > or some other way. > Yes, a thread pool is required on the server. Consequently a thread pool is a required parameter of grpc.server <https://github.com/grpc/grpc/blob/2c779d64db4b4e460c697b59170f85135d552db5/src/python/grpcio/grpc/__init__.py#L1211>. Are you not calling grpc.server to construct your server? Are you not passing a thread pool when you do? Please correct me if I am going wrong anywhere, and please suggest what can > I do to handle multiple simultaneous client requests in my Python > Implementation. > I strongly suspect that you are going wrong somewhere, but it will be hard to determine exactly where without reading your code. Please share it with us? -Nathaniel -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAEOYnATDseudqH4MMpOGF-NS5Q34-thhkGgT9za8bVU97E03rA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
