You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/roadmap.md
+18-22Lines changed: 18 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,24 @@ everything, we also need keep the balance between creating a reusable and stable
16
16
open-source solution and meeting those requirements unique to Google's Web applications
17
17
(such as search).
18
18
19
-
## Roadmap Features (in no particular order)
19
+
## Roadmap Features
20
+
21
+
### TypeScript Codebase (2024)
22
+
Migrate the codebase to TypeScript and update the related toolchains (incl. remove
23
+
dependency on `closure-compiler`). Enhance overall TypeScript support.
24
+
25
+
### Streaming Support
26
+
27
+
Enhance Fetch/streams support (e.g. cancellation support) and improve runtime
28
+
support, including service workers.
29
+
30
+
See streaming roadmap [here](streaming-roadmap.md).
31
+
32
+
### Bidi Streaming
33
+
34
+
We plan to leverage [WebTransport](https://web.dev/webtransport/) for bi-directional streaming.
35
+
36
+
Also see the dedicate road-map doc on [bidi streaming](streaming-roadmap.md).
20
37
21
38
### Non-Binary Message Encoding
22
39
@@ -28,22 +45,6 @@ For Google's Web applications (e.g. gmail), we use a JSON like format which is
28
45
comparable to JSON in efficiency but also very compact in both the message size
29
46
and code size.
30
47
31
-
### Streaming Support
32
-
33
-
Currently the gRPC-Web client library uses XHR to ensure cross-browser support
34
-
and to support platforms such as React-Native.
35
-
36
-
We do plan to add fetch/streams support at some point, which is more efficient
37
-
for binary streams and incurs less memory overhead on the client-side.
38
-
39
-
However, fetch still has certain gaps compared to XHR, most notably the lack of
40
-
cancellation support. Progressing events, I/O event throttling are other
41
-
concerns.
42
-
43
-
### Bidi Streaming
44
-
45
-
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).
46
-
47
48
### Security
48
49
49
50
We plan to publish a comprehensive guideline doc on how to create secure Web
@@ -71,11 +72,6 @@ frameworks such as Angular.
71
72
Note: Dart gRPC will use gRPC-Web as the underlying implementation on the
72
73
Dart Web platform.
73
74
74
-
### TypeScript Support
75
-
76
-
We now have experimental TypeScript Support! See the main README for more
77
-
information.
78
-
79
75
### Non-Closure compiler support
80
76
81
77
With the addition of CommonJS style imports, gRPC-Web client stubs can now be
0 commit comments