This issue is part of a project to move x/net/http2 into std: #67810
The http2.ClientConnPool type permits users to define a connection pool to be used by an http2.Transport.
This type has been entirely superseded by the client connection API added in #75772. The best way to create a user-defined connection pool is for the pool to implement the http.RoundTripper interface, using Transport.NewClientConn to create connections.
Since the HTTP/2-specific pool API no longer serves a useful purpose, I propose deprecating the following symbols in x/net/http2:
This issue is part of a project to move x/net/http2 into std: #67810
The
http2.ClientConnPooltype permits users to define a connection pool to be used by anhttp2.Transport.This type has been entirely superseded by the client connection API added in #75772. The best way to create a user-defined connection pool is for the pool to implement the
http.RoundTripperinterface, usingTransport.NewClientConnto create connections.Since the HTTP/2-specific pool API no longer serves a useful purpose, I propose deprecating the following symbols in x/net/http2:
ClientConnPoolClientConnClientConnStateTransport.NewClientConn