googleapis / googleapis/google-api-go-client
google.golang.org/api/transport/grpc: Pool over insecure connection.
- Dominant language
- Go
- Stars
- 4.5k
- Forks
- 1.5k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 32
Description
google.golang.org/api/transport/grpc provides `DialInsecure`, but it ignores `WithGRPCConnectionPool`.
Can we have `DialInsecurePool`?
or is it safe to use `DialPool` if we set `option.WithoutAuthentication()` and `grpc.WithTransportCredentials(insecure.NewCredentials())` ?
re: https://crrev.com/c/8360133
Contributor guide
Research direction
Start by reading google.golang.org/api/transport/grpc, especially DialInsecure, DialPool, and their handling of WithGRPCConnectionPool, WithoutAuthentication, and insecure.NewCredentials(). Check whether DialPool can safely provide the requested insecure pooled connection; done means either adding a supported DialInsecurePool path or documenting and validating the safe existing combination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100