| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
Appease the yapf gods
Reformat
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A process may fork after invoking grpc_init() and use gRPC in the child
if and only if the child process first destroys all gRPC resources
inherited from the parent process and invokes grpc_shutdown().
Subsequent to this, the child will be able to re-initialize and use
gRPC. After fork, the parent process will be able to continue to use
existing gRPC resources such as channels and calls without interference
from the child process.
To facilitate gRPC Python applications meeting the above constraints,
gRPC Python will automatically destroy and shutdown all gRPC Core
resources in the child's post-fork handler, including cancelling
in-flight calls (see detailed design below). From the client's
perspective, the child process is now free to create new channels and
use gRPC.
|
| | |
|
| |
|
|
|
|
|
| |
All files under `grpc/_cython/_cygrpc` in grpcio Python package
are used as include files and thus have a .pxi file extension.
grpc_gevent implementation was added in 1bfff8e, but didn't include the
.pxi file extension. Update these file names.
|
| |
|
|
|
| |
Because some cpp code ends up leaking into cython, we change
the cython generator to generate cpp code.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Rather than single classes they are now broken up into class families
with each class containing only those fields and methods that are
needed in the context in which the class is used.
|
| |
|
|
|
|
|
|
|
| |
It is now a family of classes conforming to an interface rather than a
single class no single instance of which makes use of all behavior
scoped to the class.
It also now only uses gRPC Core memory for the time of a single batch
rather than for the entire lifetime of the instance.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
Richard Belleville
Eric Gribkoff
Mehrdad Afshari
Naresh
kpayson64
Nathaniel Manista
Jan Tattermusch
Craig Tiller
murgatroid99
Masood Malekghassemi