grpc
/
grpc-web
mirror of https://github.com/grpc/grpc-web.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Roadmap update (#1484)

This commit is contained in:
Eryu Xia 2025-06-10 13:07:35 -07:00 committed by GitHub
parent 7ea072a94d
commit 70f2b595ce
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 14 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
doc/roadmap.md
View File

@ -18,7 +18,17 @@ open-source solution and meeting those requirements unique to Google's Web appli
## Roadmap Features
### TypeScript Codebase (2024)
> NOTE: Due to the status of two of gRPC-Web’s core dependencies — [Google
Closure](https://github.com/google/closure-library/issues/1214), which has been
archived, and [Protobuf
JavaScript](https://github.com/protocolbuffers/protobuf-javascript?tab=readme-ov-file#project-status),
which is receiving only minimal updates — the gRPC-Web project is no longer able
to deliver new, modern solutions for the open source community. As a result, we
do not plan to be adding new features going forward.
>
> We recommend you to use [gRPC-Gateway](https://github.com/grpc-ecosystem/grpc-gateway) as an alternative.
### TypeScript Codebase
Migrate the codebase to TypeScript and update the related toolchains (incl. remove
dependency on `closure-compiler`). Enhance overall TypeScript support.
@ -29,12 +39,6 @@ support, including service workers.
See streaming roadmap [here](streaming-roadmap.md).
### Bidi Streaming
We plan to leverage [WebTransport](https://web.dev/webtransport/) for bi-directional streaming.
Also see the dedicate road-map doc on [bidi streaming](streaming-roadmap.md).
### Non-Binary Message Encoding
The binary protobuf encoding format is not most CPU efficient for browser
@ -53,17 +57,6 @@ applications.
Native support such as XSRF, XSS prevention may also be added to the gRPC-Web
protocol.
### In-process Proxies
[In-process proxies](https://github.com/grpc/grpc-web/blob/master/doc/in-process-proxy.md)
will eliminate the need to deploy Envoy to use gRPC-Web.
We have plans to add in-process proxy support in Python, Java, Node, C++ etc. Let us know
if you are interested in implementing any language-specific in-process
gRPC-Web proxy.
To minimize maintenance overhead, we will only support Envoy as the official proxy for gRPC-Web.
### Web Framework Integration
This is to provide first-class support for gRPC API and gRPC-Web in popular Web
@ -76,12 +69,4 @@ Dart Web platform.
With the addition of CommonJS style imports, gRPC-Web client stubs can now be
compiled with various tools such as Browserify, Webpack, etc. Let us know
what else we should try!
### Web UI Support
This allows the user to construct and submit a gRPC request directly using the
browser.
We need define a standard look & feel for creating and rendering nested protobuf
messages.
what else we should try!

5
doc/streaming-roadmap.md
View File

@ -3,7 +3,6 @@
This document describes the road-map for gRPC-Web to support different streaming features.
* Server-streaming
* Client-streaming and half-duplex streaming
* Full-duplex streaming over WebTransport
## Server-streaming
@ -19,9 +18,9 @@ We don’t plan to support client-streaming via Fetch/upload-streams (See [Appen
Client-streaming and half-duplex bidi streaming will be addressed when Full-duplex streaming is supported via WebTransport (see below).
## Full-duplex streaming over WebTransport
## Full-duplex streaming
We will be leveraging [WebTransport](https://web.dev/webtransport/) to enable full-duplex (bi-directional) streaming. Planned for 2023+.
Not planned.
## Issues with WebSockets