akka/akka-http

Peer to Peer Extension to HTTP

Open

#3,757 opened on 2021年2月10日

GitHub で見る
 (7 comments) (3 reactions) (0 assignees)Scala (1,311 stars) (598 forks)batch import
1 - triageddiscusshelp wantednice-to-have (low-prio)t:coret:http2

説明

About 5 years ago @Lukasa wrote up an IETF draft named Peer-to-peer Extension to HTTP/2 which allows an HTTP connection to switch between taking on the role of a client and a server.

I found it thinking about a use case of it for Credential Negotiation described HTTP-Signature authentication for Solid.

There may be quite a lot of other use cases for very large deployments of Akka, and for inter Actor communication. I don't know. Perhaps people can use this issue to suggest interesting use cases.

I wonder how difficult something like this would be to implement, assuming that one had concluded that there were really convincing use cases for it. Also it would be interesting to know if that maps nicely to QUIC.

コントリビューターガイド

技術スタック
scala
領域
backendapi
Issue 種別
research
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
5
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
unclear
前提条件
Understanding of HTTP/2Familiarity with Akka HTTP
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
10
調査方針
This issue explores implementing a peer to peer extension to HTTP/2 in Akka HTTP, referencing an IETF draft. The discussion is open ended, asking about use cases and feasibility. To proceed, one should study the draft (draft benfield http2 p2p) and consider how Akka HTTP's existing architecture could support role switching. Also, the relation to QUIC (issue #3692) should be investigated. No concrete implementation steps are provided.