The fork support added in 1.15.0 in gRPC-Python is only for the client side. This means, on a gRPC-Python client, it is now possible to fork the process while an RPC is in progress. Typically mulitprocessing module is used to distribute your work to child processes and get the result back. For example, you could be getting streamed responses from a server and handle the response in a child process without affecting the ongoing streaming RPC in the parent process. This was previously not supported. In this
example, a datastore client forks using multiprocessing after it has created a gRPC connection and done an RPC. This didn't work prior to 1.15.0.