Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Vu Cong Tuan	69fab8eacb	Fix many typos in doc Signed-off-by: Vu Cong Tuan <tuanvc@vn.fujitsu.com>	6 years ago
Doug Fawley	b63524639b	fix minor punctuation noticed when editor removed spaces at end of line	6 years ago
Doug Fawley	a62c530465	Add protocol handshake to 'READY' connectivity requirements 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.	6 years ago
Eric Anderson	f090194666	doc: Fully define GetState in connectivity state API	7 years ago
randvis	0a588c6453	Fix the incorrect number of states There're five states: CONNECTING, READY, TRANSIENT_FAILURE, IDLE, SHUTDOWN.	8 years ago
Eric Anderson	05e8c9a8b7	Connectivity state FATAL_FAILURE doesn't exist; it is SHUTDOWN In a previous version of the document we used FATAL_FAILURE instead of SHUTDOWN. This was changed when there was no case that would cause a fatal failure other than shutdown. However, one reference to the old name was missed.	9 years ago
nmittler	25c21d8b2b	Fixing type-o	9 years ago
Abhishek Kumar	33094a7c62	More fixes to GO_AWAY spelling	10 years ago
Abhishek Kumar	783ad1e9d1	Fixed Go_AWAY to GOAWAY	10 years ago
Abhishek Kumar	56514def9e	Update connectivity-semantics-and-api.md	10 years ago
Abhishek Kumar	b66f19f1e0	Update connectivity-semantics-and-api.md	10 years ago
Eric Anderson	9855a34e1a	Add Connectivity doc This is a faithful representation of the current version of the Google Doc with only formatting changes.	10 years ago

12 Commits (d5b285df95c654980ed3af2a5b6178600ad59f2f)