| Commit message (Collapse) | Author | Age |
|\
| |
| | |
ipv6 addresses must be bracketed if using a port
|
|\ \
| | |
| | | |
Channelz Python wrapper implementation
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Expose the C-Core API in Cython layer
* Handle the object translation
* Create a separate package for Channelz specifically
* Handle nullptr and raise exception if seen one
* Translate C++ Channelz unit tests
* Adding 5 more invalid query unit tests
Adding peripheral utility for grpcio-channelz package
* Add to `pylint_code.sh`
* Add to Python build script
* Add to artifact build script
* Add to Bazel
* Add to Sphinx module list
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| | |
* Reorganize the section titles
* Add Tutorial and Example
|
|/
|
|
|
|
|
|
|
|
|
|
| |
The host/port splitting code will not pull out a port if there are >=2 colons[1].
Unit test code demos this [2]. Note other documentation gets this right[3]. Example IP came from this issue[4] and the unit tests[2].
See also: relevant RFCs [5] [6]
[1]https://github.com/grpc/grpc/blob/618a3f561d4a93f263cca23abad086ed8f4d5e86/src/core/lib/gpr/host_port.cc#L81
[2]https://github.com/grpc/grpc/blob/618a3f561d4a93f263cca23abad086ed8f4d5e86/test/core/client_channel/resolvers/sockaddr_resolver_test.cc#L107
[3]https://chromium.googlesource.com/external/github.com/grpc/grpc/+/chromium-deps/2016-07-19/src/core/ext/client_config/README.md
[4]https://github.com/grpc/grpc/issues/6623
[5]http://www.iana.org/go/rfc5952#section-6
[6]http://www.iana.org/go/rfc3986#section-3.2.3
|
|
|
|
|
|
|
|
|
| |
* Use templates instead of generating them every time
* Theme changed
* Add grpc_* modules
* APIs grouped
* No documentation for class members without docstring
* Add docstring for status code
|
|
|
|
|
|
|
| |
Callers are updated to properly initialize the memory.
This behavior can be overridden using GRPC_ARENA_INIT_STRATEGY
environment variable.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When security is disabled, not waiting for the HTTP/2 handshake can lead to
DoS-style behavior. For details, see:
https://github.com/grpc/grpc-go/issues/954. This requirement will incur an
extra half-RTT latency before the first RPC can be sent under plaintext, but
this is negligible and unencrypted connections are rarer than secure ones.
Under TLS, the server will effectively send its part of the HTTP/2 handshake
along with its final TLS "server finished" message, which the client must wait
for before transmitting any data securely. This means virtually no extra
latency is incurred by this requirement.
Go had attempted to separate "connection ready" with "connection successful"
(Issue: https://github.com/grpc/grpc-go/issues/1444 PR:
https://github.com/grpc/grpc-go/pull/1648). However, this is confusing to
users and introduces an arbitrary distinction between these two events. It has
led to several bugs in our reconnection logic (e.g.s
https://github.com/grpc/grpc-go/pull/2380,
https://github.com/grpc/grpc-go/pull/2391,
https://github.com/grpc/grpc-go/pull/2392), due to the complexity, and it makes
custom transports (https://github.com/grpc/proposal/pull/103) more difficult
for users to implement.
We are aware of some use cases (in particular,
https://github.com/soheilhy/cmux) expecting the behavior of transmitting an RPC
before the HTTP/2 handshake is completed. Before making behavior changes to
implement this, we will reach out to our users to the best of our abilities.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Keepalive watchdog firing should return status UNAVAILABLE
|
| | |
|
|/ |
|
| |
|
|\ |
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|\
| |
| | |
Update naming documentation.
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Cast an index to size_t to avoid sign-conversion warning
|
|\ \ \
| | | |
| | | | |
Fix a number of spelling errors.
|
| | |/
| |/| |
|
|/ / |
|
| | |
|
|\ \
| |/
|/| |
Update instructions to include how to satisfy gFlags prerequisite on a Mac
|
|\ \
| | |
| | | |
Use environment variable to enable CFStream
|
|\ \ \
| | | |
| | | | |
Create ssl-performance.md
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | | |
First draft
|
| |/ / |
|
| |/ |
|
|/ |
|
| |
|