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

Commit Graph

Author	SHA1	Message	Date
Muxi Yan	0e00c43082	Move headers from grpc++ to grpcpp	7 years ago
Jan Tattermusch	7897ae9308	auto-fix most of licenses	8 years ago
Alexander Polcyn	bb2c338924	format changes, address comments	8 years ago
Alexander Polcyn	0f02908e67	address comments	8 years ago
Alexander Polcyn	d809a15ec4	cpp doc nits	8 years ago
Vijay Pai	84033b1f6b	Stick to StatusCode::INTERNAL when there's no service response on a StreamedUnary	8 years ago
Vijay Pai	a9c0d7f88b	Change names to StreamedUnary, ServerUnaryStreamer, etc. Use a templated method handler since most code shared between the new StreamedUnary and the existing BidiStreaming. Eliminate the separate enum case for streamed unary. Return a status failure if a StreamedUnary method handler doesn't actually do a write (since that is violating the appearance of unary-ness)	8 years ago
Alistair Veitch	75d5c0f024	post merge	9 years ago
David Garcia Quintas	08a0a3306e	Made "codedgen" directories closed over #includes	9 years ago
Craig Tiller	d6599a39e4	Replicate C++ docs from master to beta branch Original PR #3074 by @dgquintas	9 years ago
Craig Tiller	00ad71c135	Revert "C++ docs"	9 years ago
David Garcia Quintas	c5318a2aa7	MOAR COMMENTS	9 years ago
yang-g	9e2f90cd06	headers reorg	9 years ago
Eric Anderson	5b53e35ba4	Remove HTTP mappings from status.h The mappings are a combination of useless, inaccurate, and harmful. Leave them out until they are helpful and correct. Fundamental issues: - If in need of mappings, a user would need HTTP -> gRPC code mappings. But the docs don't provide that since the mappings are not 1:1. - There _is no_ gRPC -> HTTP code mapping taking place in gRPC. This may change in the future, but until then the docs are misleading. But even given those were resolved, there are additional issues. Two obvious examples: - 501 Not Implemented is refering to HTTP methods such as GET and POST not being implement. That should not be used for gRPC methods not found (UNIMPLEMENTED). - 404 Not Found is for when the resource is not found. In gRPC, the resource is the gRPC method, not the parameters (NOT_FOUND). If there is a REST conversion layer on top of gRPC, then 404 would be appropriate, but that just shows that the mapping can not be canonical.	10 years ago
Nicolas "Pixel" Noble	1ff52d5278	Guard headers tool.	10 years ago
Craig Tiller	190d360def	Add missing new-lines at end of file	10 years ago
Craig Tiller	0605995e55	Update copyright to 2015	10 years ago
Craig Tiller	b5dcec5a2e	clang-format codebase	10 years ago
Nicolas Noble	b7ebd3b8c6	Initial import.	10 years ago

1 Commits (04a6b8467c4d2ac0d30561f75e1260a9e9ede983)