You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to grpc.io
Hey all,
I am using a single stub to create multiple RPC calls in my program, and the program will create another RPC call without the previous RPC call being finished, I would like to know if this is feasible, and can the stub manage multiple RPC calls in a single-threaded environment?
Thanks,
Sui Ma
Mehrdad Afshari
unread,
Sep 20, 2024, 1:04:20 PM9/20/24
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to grpc.io
You can certainly share a stub for multiple RPCs; it is often a recommended practice [in most gRPC languages]. I am not sure what you mean by single-threaded environment though? gRPC core itself will spin up threads as necessary but your application logic can be a single thread/async.