- Mar 04, 2015
-
-
Nicolas "Pixel" Noble authored
-
- Mar 03, 2015
-
-
Qi Zhao authored
Revert "dockerfiles/go: go install from GOPATH and remove bash from CMD"
-
Qi Zhao authored
-
Nicolas Noble authored
Improved Makefile protoc message
-
- Mar 02, 2015
-
-
murgatroid99 authored
-
Nicolas Noble authored
Hookup TSI tracer
-
Nicolas Noble authored
Deflake fling_test
-
Nicolas Noble authored
Added python tests to .travis.yml
-
murgatroid99 authored
-
murgatroid99 authored
-
murgatroid99 authored
-
murgatroid99 authored
-
murgatroid99 authored
-
murgatroid99 authored
-
Craig Tiller authored
-
Masood Malekghassemi authored
Update Python codegen to early_adopter interface
-
murgatroid99 authored
-
Craig Tiller authored
-
Nicolas Noble authored
Removed execute permissions from README files.
-
Tim Emiola authored
Docker files for c# (on mono)
-
murgatroid99 authored
-
murgatroid99 authored
-
murgatroid99 authored
-
Jan Tattermusch authored
-
murgatroid99 authored
-
Craig Tiller authored
Remove HTTP mappings from status.h
-
Craig Tiller authored
Also, make the flaky: tag a little more visible in build.json
-
Craig Tiller authored
-
Craig Tiller authored
Make debugging a little easier, and remove an unnecessary assert
-
Tim Emiola authored
dockerfiles/go: go install from GOPATH and remove bash from CMD
-
Eric Anderson authored
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.
-
Craig Tiller authored
-
Craig Tiller authored
-
Craig Tiller authored
-
Craig Tiller authored
-
Craig Tiller authored
-
Misha Brukman authored
-
Craig Tiller authored
-
Craig Tiller authored
-
Nathaniel Manista authored
Fixes #898.
-