https://github.com/bradfitz/exp-httpclient

experimental new HTTP client API for #golang (WIP)
https://github.com/bradfitz/exp-httpclient

Last synced: 13 days ago
JSON representation

experimental new HTTP client API for #golang (WIP)

• Host: GitHub
• URL: https://github.com/bradfitz/exp-httpclient
• Owner: bradfitz
• Created: 2018-09-10T16:14:09.000Z (about 6 years ago)
• Default Branch: master
• Last Pushed: 2019-01-01T18:36:05.000Z (almost 6 years ago)
• Last Synced: 2024-10-14T16:29:56.709Z (25 days ago)
• Language: Go
• Homepage:
• Size: 18.6 KB
• Stars: 584
• Watchers: 55
• Forks: 13
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• favorite-link - 用于#golang (WIP) 的实验性新 HTTP 客户端 API。

README

        
# Rethinking Go's HTTP client

This repository explores redesigning the API for

the [Go language](https://golang.org/)'s

[`net/http`](https://golang.org/pkg/net/http/)

[`Client`](https://golang.org/pkg/net/http/#Client) and 

[`Transport`](https://golang.org/pkg/net/http/#Transport).

Initially, though, it collects problems with the current API. The

actual solution has not yet been designed.

# FAQ

## What's wrong with Go's HTTP client?

See the [list of problems](problems.md).

Or see the [overview presentation](https://docs.google.com/presentation/d/e/2PACX-1vTTFQjMSxai7TvhBJgkJf4K3RrT3tJrP7KUQ3rZB8e4UL7grCnxQh7o4yYYvyYugnkcfVwvTrwA23B0/pub?start=false&loop=false&delayms=3000) for the problems in a different format.

## What about the Server?

This repo does not aim to address the server side of the `net/http`

package. The server half is in better shape than the client, and it's

also easier to fix the client half without fragmenting the

ecosystem. Changing the Server interface needs to be done much more

carefully.

But even long term, it's almost certainly best for the client and server to

live in separate packages. They might share some types & code from

shared HTTP package(s).

## Who's leading this effort?

Brad Fitzpatrick, [@bradfitz](https://github.com/bradfitz). I've owned

the net/http package for over 8 years and have plenty of gripes about

it. I welcome all input. If we're going to finally change it, we

should get it right, so there's no need to rush this process.

## Contributing

This repo is temporary and doesn't accept PRs and issues are disabled.

It will move at some point to Go's repos with Go's bots and policies.

For now, discuss at https://github.com/golang/go/issues/23707

## What's the plan?

Roughly:

* Iterate on the API & godoc repeatedly until it looks right (with a fake, `panic("TODO")`-only implementation)

* Discuss, revise.

* Add a temporary implementation (likely inefficient), wrapping the existing net/http Client.

* Port code to use it. See if we're still happy.

* Discuss, revise.

* Copy `net/http` and `golang.org/x/net/http2` code into `httpclient` (likely several packages).

* Benchmark, tune, revise API as needed.

* Redo the "legacy" `net/http` and `golang.org/x/net/http2` client APIs as wrappers around `httpclient`

Of course, this is all up for debate.