connect-go
connect-go copied to clipboard
The Go implementation of Connect: Protobuf RPC that works.
**Describe the solution you'd like** To support capturing tracing data, it would be amazing to add out-of-the-box support for the OpenTelemetry standard into the `connect-go` client/server. This would likely be...
This isn't a specific issue or proposal. Instead, it outlines the work we need to finish before we tag a stable release of `connect-go`. We're planning to complete all these...
The mapping from connect error codes to HTTP status codes is currently private and not accessible to users who are implementing connect in their existing HTTP servers. This helper has...
**Is your feature request related to a problem? Please describe.** Even though Connect handlers work with `net/http` middleware, it's often necessary to re-implement existing HTTP middleware as Connect interceptors so...
**Is your feature request related to a problem? Please describe.** Nope. This isn't directly related to connect-go per se but to other packages made available by bufbuild. I notice there...
gRPC has been around for quite a while now. Lots of organizations have lots of existing code using the client stubs and server interfaces generated by `protoc-gen-go-grpc` (or its predecessor,...
**Is your feature request related to a problem? Please describe.** I'm struggling to understand how to implement a logging/tracing interceptor for the full Client/Server side streams. Something similar to how...
When using `net/http` middleware to wrap handlers and collect logs or metrics, it's nice to be able to parse out the protobuf package name, service name, and procedure name. However,...
Talked to @robbertvanginkel about this for a while today: in short, the problem is that clients can't tell whether an `*Error` was sent by the server, or whether it was...
Within gRPC, one big feature is service discovery via xDS and other client side load balancing features. This is actually one of the biggest selling points imo for running gRPC...