You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@fory.apache.org by ch...@apache.org on 2026/08/04 05:58:38 UTC
(fory-site) 09/11: 🔄 synced local 'docs/grpc/' with remote 'docs/grpc/'
This is an automated email from the ASF dual-hosted git repository.
chaokunyang pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/fory-site.git
commit ddba7f46230079821e856196e3086fedb78e304e
Author: chaokunyang <sh...@gmail.com>
AuthorDate: Tue Aug 4 05:58:24 2026 +0000
🔄 synced local 'docs/grpc/' with remote 'docs/grpc/'
---
docs/grpc/cpp.md | 4 ++--
docs/grpc/csharp.md | 2 +-
docs/grpc/go.md | 2 +-
docs/grpc/index.md | 18 +++++++++---------
docs/grpc/java.md | 2 +-
docs/grpc/javascript.md | 2 +-
docs/grpc/kotlin.md | 2 +-
docs/grpc/python.md | 2 +-
docs/grpc/rust.md | 2 +-
docs/grpc/scala.md | 2 +-
docs/grpc/troubleshooting.md | 4 ++--
11 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/docs/grpc/cpp.md b/docs/grpc/cpp.md
index 499cb51c1c..c5d87e947d 100644
--- a/docs/grpc/cpp.md
+++ b/docs/grpc/cpp.md
@@ -114,7 +114,7 @@ For this schema, the C++ generator emits:
Include the generated gRPC header from application code and compile
`demo_greeter.service.grpc.cc` once in your build target. The codec is generated
-directly in the gRPC header; there is no separate Fory gRPC runtime source file.
+directly in the gRPC header; there is no separate Fory gRPC support source file.
## Implement a Server
@@ -245,7 +245,7 @@ the final status.
The generated descriptors preserve the exact IDL service and method names for
the gRPC path.
-## gRPC Runtime Behavior
+## gRPC Stack Behavior
The generated service companion only supplies Fory serialization and gRPC C++
bindings. Operational behavior remains standard gRPC C++ behavior:
diff --git a/docs/grpc/csharp.md b/docs/grpc/csharp.md
index fb468cf831..06997d1e7b 100644
--- a/docs/grpc/csharp.md
+++ b/docs/grpc/csharp.md
@@ -284,7 +284,7 @@ A gRPC service named `Greeter` still generates the service companion
schema files target the same C# namespace without colliding. No
namespace-derived or service-derived module alias is generated.
-## gRPC Runtime Behavior
+## gRPC Stack Behavior
The generated service code only replaces request and response serialization.
All normal gRPC operational features still belong to your gRPC stack:
diff --git a/docs/grpc/go.md b/docs/grpc/go.md
index b3551d96a1..ee3ec18d75 100644
--- a/docs/grpc/go.md
+++ b/docs/grpc/go.md
@@ -201,7 +201,7 @@ Generated Go code follows grpc-go conventions:
- The generated codec is used for every message frame, including streaming
frames.
-## gRPC Runtime Behavior
+## gRPC Stack Behavior
The generated service companion only supplies Fory serialization. Operational
behavior remains standard grpc-go behavior:
diff --git a/docs/grpc/index.md b/docs/grpc/index.md
index a0c4712e0a..0aae10ce69 100644
--- a/docs/grpc/index.md
+++ b/docs/grpc/index.md
@@ -25,7 +25,7 @@ the Fory compiler. The payload marshaller uses Fory rather than protobuf message
## When to Use It
Use Fory gRPC when every peer is generated from the same Fory IDL, protobuf IDL, or FlatBuffers IDL
-contract and supports the matching Fory runtime. Use ordinary protobuf gRPC when generic protobuf
+contract and supports the matching Fory implementation for its language. Use ordinary protobuf gRPC when generic protobuf
clients, reflection tools, or protobuf message bytes are required.
## Schema Frontends
@@ -45,7 +45,7 @@ project build.
1. Define messages and services in a supported compiler frontend.
2. Generate models and gRPC companions with `foryc`.
-3. Add the normal gRPC dependencies for the selected runtime.
+3. Add the normal gRPC dependencies for the selected language.
4. Implement the generated server base and call the generated client.
5. Verify unary and streaming calls between generated peers.
@@ -62,19 +62,19 @@ generated request and response models.
### Ownership Boundary
-Fory can generate service companions for application-provided gRPC runtimes. Those companions
+Fory can generate service companions for application-provided gRPC implementations. Those companions
provide Fory serialization for request and response objects; the application and gRPC stack still
own listeners, channels, credentials, authentication, authorization, deadlines, retries, and
transport lifecycle.
Fory packages do not add a gRPC implementation as a hard dependency. The application selects and
-configures the runtime's gRPC libraries.
+configures its gRPC libraries.
### Generated Service Surface
-The compiler emits runtime-idiomatic service bases, clients or stubs, method metadata, and Fory
+The compiler emits language-idiomatic service bases, clients or stubs, method metadata, and Fory
marshallers. Model generation is documented under
-[Generated Code](../compiler/generated-code/index.md); the runtime pages document server and client
+[Generated Code](../compiler/generated-code/index.md); the language pages document server and client
integration.
## Interoperability
@@ -94,13 +94,13 @@ Test at least one unary call and every streaming shape used by the service. A pr
`UNIMPLEMENTED` or decode failure usually means the peer used an ordinary protobuf stub or a
different generated service contract.
-## Runtime Guides
+## Language Guides
Java, Python, C++, Go, Rust, JavaScript/TypeScript, C#, Dart, Scala, and Kotlin have documented gRPC
-companions. Use the [support matrix](../introduction/support-matrix.md) and the selected runtime page
+companions. Use the [support matrix](../introduction/support-matrix.md) and the selected language page
for current dependencies and streaming support.
-| Runtime | Guide |
+| Language | Guide |
| --------------------- | ------------------------------------- |
| Java | [Java](java.md) |
| Python | [Python](python.md) |
diff --git a/docs/grpc/java.md b/docs/grpc/java.md
index 555a029e81..96f92952cd 100644
--- a/docs/grpc/java.md
+++ b/docs/grpc/java.md
@@ -366,7 +366,7 @@ final class StreamingClient {
The generated descriptors preserve the exact IDL service and method names for
the gRPC path.
-## gRPC Runtime Behavior
+## gRPC Stack Behavior
The generated service code only replaces request and response serialization.
All normal gRPC operational features still belong to grpc-java:
diff --git a/docs/grpc/javascript.md b/docs/grpc/javascript.md
index 2c0a623007..3f4c94faa9 100644
--- a/docs/grpc/javascript.md
+++ b/docs/grpc/javascript.md
@@ -291,7 +291,7 @@ stream.on("end", () => {
});
```
-## gRPC Runtime Behavior
+## gRPC Stack Behavior
Generated service code only replaces request and response serialization. Normal
gRPC operational features still belong to the transport package:
diff --git a/docs/grpc/kotlin.md b/docs/grpc/kotlin.md
index 09f87223d0..5cfc682f81 100644
--- a/docs/grpc/kotlin.md
+++ b/docs/grpc/kotlin.md
@@ -230,7 +230,7 @@ stub.chat(
}
```
-## gRPC Runtime Behavior
+## gRPC Stack Behavior
The generated service code only replaces request and response serialization.
All normal gRPC operational features still belong to grpc-java and
diff --git a/docs/grpc/python.md b/docs/grpc/python.md
index c8bb3f69d4..0d271023b2 100644
--- a/docs/grpc/python.md
+++ b/docs/grpc/python.md
@@ -279,7 +279,7 @@ with grpc.insecure_channel("localhost:50051") as channel:
Sync streaming follows the normal `grpcio` iterator and generator conventions.
-## gRPC Runtime Behavior
+## gRPC Stack Behavior
The generated service companion only supplies Fory serialization callbacks.
Operational behavior remains standard `grpcio` behavior:
diff --git a/docs/grpc/rust.md b/docs/grpc/rust.md
index fe2d2b775f..4ddaf3dd64 100644
--- a/docs/grpc/rust.md
+++ b/docs/grpc/rust.md
@@ -300,7 +300,7 @@ reference metadata for a request or response type, Rust gRPC generation rejects
that service. Use thread-safe reference shapes for gRPC payloads, or keep the
non-thread-safe type out of the RPC boundary.
-## gRPC Runtime Behavior
+## gRPC Stack Behavior
The generated service companion only supplies Fory serialization and tonic
bindings. Operational behavior remains standard tonic behavior:
diff --git a/docs/grpc/scala.md b/docs/grpc/scala.md
index 43e9386b3e..43d5122b26 100644
--- a/docs/grpc/scala.md
+++ b/docs/grpc/scala.md
@@ -371,7 +371,7 @@ Server-streaming, client-streaming, and bidirectional server methods use
grpc-java `StreamObserver` APIs because streaming completion, request flow
control, cancellation, and backpressure follow grpc-java behavior.
-## gRPC Runtime Behavior
+## gRPC Stack Behavior
The generated service code only replaces request and response serialization.
All normal gRPC operational features still belong to grpc-java:
diff --git a/docs/grpc/troubleshooting.md b/docs/grpc/troubleshooting.md
index 916e816bb2..71c0c163cf 100644
--- a/docs/grpc/troubleshooting.md
+++ b/docs/grpc/troubleshooting.md
@@ -19,7 +19,7 @@ license: |
limitations under the License.
---
-Use the selected runtime guide for dependency- and API-specific diagnostics.
+Use the selected language guide for dependency- and API-specific diagnostics.
## `UNIMPLEMENTED`
@@ -33,5 +33,5 @@ separate ordinary protobuf service.
## A generated file does not compile
-Check the runtime page's required gRPC packages and versions, then regenerate all model and service
+Check the language page's required gRPC packages and versions, then regenerate all model and service
files with the same compiler version.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@fory.apache.org
For additional commands, e-mail: commits-help@fory.apache.org