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
The following commit(s) were added to refs/heads/main by this push:
new af72b8e63 Fix trademark issue7 (#317)
af72b8e63 is described below
commit af72b8e63407fadfd264e0fa1dafbe843c2e4524
Author: Shawn Yang <[email protected]>
AuthorDate: Fri Sep 12 11:06:50 2025 +0800
Fix trademark issue7 (#317)
---
blog/2024-07-23-fury_0_6_0_release.md | 12 ++++----
blog/2024-08-04-fury_0_7_0_release.md | 36 +++++++++++-----------
docs/docs/introduction/benchmark.md | 4 +--
.../current/docs/guide/java_serialization_guide.md | 2 +-
.../docs/guide/java_serialization_guide.md | 2 +-
.../docs/guide/java_serialization_guide.md | 2 +-
.../version-0.12/guide/java_serialization_guide.md | 2 +-
src/pages/download/index.md | 4 +--
.../version-0.11/docs/introduction/benchmark.md | 4 +--
.../version-0.11/docs/introduction/introduction.md | 16 +++++-----
.../version-0.12/docs/introduction/benchmark.md | 4 +--
.../version-0.12/docs/introduction/introduction.md | 16 +++++-----
12 files changed, 52 insertions(+), 52 deletions(-)
diff --git a/blog/2024-07-23-fury_0_6_0_release.md
b/blog/2024-07-23-fury_0_6_0_release.md
index aeb933f8d..14d3ad8cb 100644
--- a/blog/2024-07-23-fury_0_6_0_release.md
+++ b/blog/2024-07-23-fury_0_6_0_release.md
@@ -84,12 +84,12 @@ protobuf_serialize thrpt 30 10060.293 ±
706.064 ops/s
Size:
-| Lib | Serialized Payload Size |
-|-----|-------------------------|
-| fury | 8077|
-| furystrict | 8009 |
-| furykv | 48028 |
-| protobuf | 18000 |
+| Lib | Serialized Payload Size |
+| ---------- | ----------------------- |
+| fury | 8077 |
+| furystrict | 8009 |
+| furykv | 48028 |
+| protobuf | 18000 |
## Feature
diff --git a/blog/2024-08-04-fury_0_7_0_release.md
b/blog/2024-08-04-fury_0_7_0_release.md
index 9fa8b8b01..06d7b1a1a 100644
--- a/blog/2024-08-04-fury_0_7_0_release.md
+++ b/blog/2024-08-04-fury_0_7_0_release.md
@@ -22,24 +22,24 @@ SomeClass copied = fury.copy(a);
Benchmark result:
-| Benchmark | objectType | Score | Error | Units |
-|-------------------------------|---------------|---------------|---------------|-------|
-| fury_copy | MEDIA_CONTENT | 1243297.690 | ± 451828.452 | ops/s |
-| fury_copy | SAMPLE | 2670545.816 | ± 1378536.021 | ops/s |
-| fury_copy | STRUCT | 2673356.422 | ± 202288.322 | ops/s |
-| fury_copy | STRUCT2 | 1943587.774 | ± 392513.707 | ops/s |
-| fury_copy_int_map | int map | 1470264.733 | ± 1021875.257 | ops/s |
-| fury_copy_list | int list | 3556892.276 | ± 127410.724 | ops/s |
-| fury_copy_object_array | array | 4430589.112 | ± 25366.893 | ops/s |
-| fury_copy_string_map | string map | 1736145.327 | ± 377806.877 | ops/s |
-| kryo_copy | MEDIA_CONTENT | 804208.092 | ± 27429.069 | ops/s |
-| kryo_copy | SAMPLE | 717669.608 | ± 71093.370 | ops/s |
-| kryo_copy | STRUCT | 1076048.642 | ± 223194.146 | ops/s |
-| kryo_copy | STRUCT2 | 141374.767 | ± 14150.535 | ops/s |
-| kryo_copy_int_map | int map | 546203.187 | ± 54669.173 | ops/s |
-| kryo_copy_list | int list | 843643.496 | ± 312306.921 | ops/s |
-| kryo_copy_object_array | object array | 1593267.344 | ± 1721824.436 | ops/s |
-| kryo_copy_string_map | string map | 574809.875 | ± 47316.340 | ops/s |
+| Benchmark | objectType | Score | Error | Units
|
+| ---------------------- | ------------- | ----------- | ------------- | -----
|
+| fury_copy | MEDIA_CONTENT | 1243297.690 | ± 451828.452 | ops/s
|
+| fury_copy | SAMPLE | 2670545.816 | ± 1378536.021 | ops/s
|
+| fury_copy | STRUCT | 2673356.422 | ± 202288.322 | ops/s
|
+| fury_copy | STRUCT2 | 1943587.774 | ± 392513.707 | ops/s
|
+| fury_copy_int_map | int map | 1470264.733 | ± 1021875.257 | ops/s
|
+| fury_copy_list | int list | 3556892.276 | ± 127410.724 | ops/s
|
+| fury_copy_object_array | array | 4430589.112 | ± 25366.893 | ops/s
|
+| fury_copy_string_map | string map | 1736145.327 | ± 377806.877 | ops/s
|
+| kryo_copy | MEDIA_CONTENT | 804208.092 | ± 27429.069 | ops/s
|
+| kryo_copy | SAMPLE | 717669.608 | ± 71093.370 | ops/s
|
+| kryo_copy | STRUCT | 1076048.642 | ± 223194.146 | ops/s
|
+| kryo_copy | STRUCT2 | 141374.767 | ± 14150.535 | ops/s
|
+| kryo_copy_int_map | int map | 546203.187 | ± 54669.173 | ops/s
|
+| kryo_copy_list | int list | 843643.496 | ± 312306.921 | ops/s
|
+| kryo_copy_object_array | object array | 1593267.344 | ± 1721824.436 | ops/s
|
+| kryo_copy_string_map | string map | 574809.875 | ± 47316.340 | ops/s
|
## Features
diff --git a/docs/docs/introduction/benchmark.md
b/docs/docs/introduction/benchmark.md
index 37693094b..ba00a0fd0 100644
--- a/docs/docs/introduction/benchmark.md
+++ b/docs/docs/introduction/benchmark.md
@@ -9,8 +9,8 @@ Different serialization frameworks are suitable for different
scenarios, and ben
If you need to benchmark for your specific scenario, make sure all
serialization frameworks are appropriately configured for that scenario.
Dynamic serialization frameworks supports polymorphism and reference, which
has more cost compared
-to static serialization frameworks, unless it uses the jit techniques as fory
did.
-Since fory will generate code at runtime, please warm up before collecting
benchmark statistics.
+to static serialization frameworks, unless it uses the jit techniques as
Apache Fory™ did.
+Since Apache Fory™ will generate code at runtime, please warm up before
collecting benchmark statistics.
### Java Serialization
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/docs/guide/java_serialization_guide.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/docs/guide/java_serialization_guide.md
index a76761daa..996f3cb50 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/docs/guide/java_serialization_guide.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/docs/guide/java_serialization_guide.md
@@ -111,7 +111,7 @@ public class Example {
| `compressLong` | 是否启用 long 压缩以减小序列化体积。
| `true`
|
| `compressString` | 是否启用字符串压缩以减小序列化体积。
| `false`
|
| `classLoader` | 类加载器不建议动态变更，Fory 会缓存类元数据。如需变更类加载器，请使用
`LoaderBinding` 或 `ThreadSafeFory`。
| `Thread.currentThread().getContextClassLoader()`
|
-| `compatibleMode` | 类型前向/后向兼容性配置。与 `checkClassVersion`
配置相关。`SCHEMA_CONSISTENT`：序列化端与反序列化端类结构需一致。`COMPATIBLE`：序列化端与反序列化端类结构可不同，可独立增删字段。[详见](#类结构不一致与版本校验)。
| `CompatibleMode.SCHEMA_CONSISTENT`
|
+| `compatibleMode` | 类型前向/后向兼容性配置。与 `checkClassVersion`
配置相关。`SCHEMA_CONSISTENT`：序列化端与反序列化端类结构需一致。`COMPATIBLE`：序列化端与反序列化端类结构可不同，可独立增删字段。[详见](#类结构不一致与版本校验)。
|
`CompatibleMode.SCHEMA_CONSISTENT` |
| `checkClassVersion` | 是否校验类结构一致性。启用后，Fory 会写入并校验
`classVersionHash`。若启用 `CompatibleMode#COMPATIBLE`，此项会自动关闭。除非能确保类不会演化，否则不建议关闭。
| `false`
|
| `checkJdkClassSerializable` | 是否校验 `java.*` 下的类实现了 `Serializable`
接口。若未实现，Fory 会抛出 `UnsupportedOperationException`。
| `true`
|
| `registerGuavaTypes` | 是否预注册 Guava 类型（如
`RegularImmutableMap`/`RegularImmutableList`）。这些类型虽非公开 API，但较为稳定。
| `true`
|
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11/docs/guide/java_serialization_guide.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11/docs/guide/java_serialization_guide.md
index a76761daa..996f3cb50 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11/docs/guide/java_serialization_guide.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11/docs/guide/java_serialization_guide.md
@@ -111,7 +111,7 @@ public class Example {
| `compressLong` | 是否启用 long 压缩以减小序列化体积。
| `true`
|
| `compressString` | 是否启用字符串压缩以减小序列化体积。
| `false`
|
| `classLoader` | 类加载器不建议动态变更，Fory 会缓存类元数据。如需变更类加载器，请使用
`LoaderBinding` 或 `ThreadSafeFory`。
| `Thread.currentThread().getContextClassLoader()`
|
-| `compatibleMode` | 类型前向/后向兼容性配置。与 `checkClassVersion`
配置相关。`SCHEMA_CONSISTENT`：序列化端与反序列化端类结构需一致。`COMPATIBLE`：序列化端与反序列化端类结构可不同，可独立增删字段。[详见](#类结构不一致与版本校验)。
| `CompatibleMode.SCHEMA_CONSISTENT`
|
+| `compatibleMode` | 类型前向/后向兼容性配置。与 `checkClassVersion`
配置相关。`SCHEMA_CONSISTENT`：序列化端与反序列化端类结构需一致。`COMPATIBLE`：序列化端与反序列化端类结构可不同，可独立增删字段。[详见](#类结构不一致与版本校验)。
|
`CompatibleMode.SCHEMA_CONSISTENT` |
| `checkClassVersion` | 是否校验类结构一致性。启用后，Fory 会写入并校验
`classVersionHash`。若启用 `CompatibleMode#COMPATIBLE`，此项会自动关闭。除非能确保类不会演化，否则不建议关闭。
| `false`
|
| `checkJdkClassSerializable` | 是否校验 `java.*` 下的类实现了 `Serializable`
接口。若未实现，Fory 会抛出 `UnsupportedOperationException`。
| `true`
|
| `registerGuavaTypes` | 是否预注册 Guava 类型（如
`RegularImmutableMap`/`RegularImmutableList`）。这些类型虽非公开 API，但较为稳定。
| `true`
|
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.12/docs/guide/java_serialization_guide.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.12/docs/guide/java_serialization_guide.md
index a76761daa..996f3cb50 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.12/docs/guide/java_serialization_guide.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.12/docs/guide/java_serialization_guide.md
@@ -111,7 +111,7 @@ public class Example {
| `compressLong` | 是否启用 long 压缩以减小序列化体积。
| `true`
|
| `compressString` | 是否启用字符串压缩以减小序列化体积。
| `false`
|
| `classLoader` | 类加载器不建议动态变更，Fory 会缓存类元数据。如需变更类加载器，请使用
`LoaderBinding` 或 `ThreadSafeFory`。
| `Thread.currentThread().getContextClassLoader()`
|
-| `compatibleMode` | 类型前向/后向兼容性配置。与 `checkClassVersion`
配置相关。`SCHEMA_CONSISTENT`：序列化端与反序列化端类结构需一致。`COMPATIBLE`：序列化端与反序列化端类结构可不同，可独立增删字段。[详见](#类结构不一致与版本校验)。
| `CompatibleMode.SCHEMA_CONSISTENT`
|
+| `compatibleMode` | 类型前向/后向兼容性配置。与 `checkClassVersion`
配置相关。`SCHEMA_CONSISTENT`：序列化端与反序列化端类结构需一致。`COMPATIBLE`：序列化端与反序列化端类结构可不同，可独立增删字段。[详见](#类结构不一致与版本校验)。
|
`CompatibleMode.SCHEMA_CONSISTENT` |
| `checkClassVersion` | 是否校验类结构一致性。启用后，Fory 会写入并校验
`classVersionHash`。若启用 `CompatibleMode#COMPATIBLE`，此项会自动关闭。除非能确保类不会演化，否则不建议关闭。
| `false`
|
| `checkJdkClassSerializable` | 是否校验 `java.*` 下的类实现了 `Serializable`
接口。若未实现，Fory 会抛出 `UnsupportedOperationException`。
| `true`
|
| `registerGuavaTypes` | 是否预注册 Guava 类型（如
`RegularImmutableMap`/`RegularImmutableList`）。这些类型虽非公开 API，但较为稳定。
| `true`
|
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.12/guide/java_serialization_guide.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.12/guide/java_serialization_guide.md
index a76761daa..996f3cb50 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.12/guide/java_serialization_guide.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.12/guide/java_serialization_guide.md
@@ -111,7 +111,7 @@ public class Example {
| `compressLong` | 是否启用 long 压缩以减小序列化体积。
| `true`
|
| `compressString` | 是否启用字符串压缩以减小序列化体积。
| `false`
|
| `classLoader` | 类加载器不建议动态变更，Fory 会缓存类元数据。如需变更类加载器，请使用
`LoaderBinding` 或 `ThreadSafeFory`。
| `Thread.currentThread().getContextClassLoader()`
|
-| `compatibleMode` | 类型前向/后向兼容性配置。与 `checkClassVersion`
配置相关。`SCHEMA_CONSISTENT`：序列化端与反序列化端类结构需一致。`COMPATIBLE`：序列化端与反序列化端类结构可不同，可独立增删字段。[详见](#类结构不一致与版本校验)。
| `CompatibleMode.SCHEMA_CONSISTENT`
|
+| `compatibleMode` | 类型前向/后向兼容性配置。与 `checkClassVersion`
配置相关。`SCHEMA_CONSISTENT`：序列化端与反序列化端类结构需一致。`COMPATIBLE`：序列化端与反序列化端类结构可不同，可独立增删字段。[详见](#类结构不一致与版本校验)。
|
`CompatibleMode.SCHEMA_CONSISTENT` |
| `checkClassVersion` | 是否校验类结构一致性。启用后，Fory 会写入并校验
`classVersionHash`。若启用 `CompatibleMode#COMPATIBLE`，此项会自动关闭。除非能确保类不会演化，否则不建议关闭。
| `false`
|
| `checkJdkClassSerializable` | 是否校验 `java.*` 下的类实现了 `Serializable`
接口。若未实现，Fory 会抛出 `UnsupportedOperationException`。
| `true`
|
| `registerGuavaTypes` | 是否预注册 Guava 类型（如
`RegularImmutableMap`/`RegularImmutableList`）。这些类型虽非公开 API，但较为稳定。
| `true`
|
diff --git a/src/pages/download/index.md b/src/pages/download/index.md
index c60f3bc20..cadd34ae6 100644
--- a/src/pages/download/index.md
+++ b/src/pages/download/index.md
@@ -11,8 +11,8 @@ For binary install, please see Apache Fory™
[install](/docs/docs/start/install
The latest source release is 0.12.2:
-| Version | Date | Source
| Release Notes
|
-|---------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|
+| Version | Date | Source
| Release Notes
|
+| ------- | ---------- |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| -------------------------------------------------------------------- |
| 0.12.2 | 2025-09-01 |
[source](https://www.apache.org/dyn/closer.lua/fory/0.12.2/apache-fory-0.12.2-src.tar.gz?action=download)
[asc](https://downloads.apache.org/fory/0.12.2/apache-fory-0.12.2-src.tar.gz.asc)
[sha512](https://downloads.apache.org/fory/0.12.2/apache-fory-0.12.2-src.tar.gz.sha512)
| [release notes](https://github.com/apache/fory/releases/tag/v0.12.2) |
## All archived releases
diff --git a/versioned_docs/version-0.11/docs/introduction/benchmark.md
b/versioned_docs/version-0.11/docs/introduction/benchmark.md
index 37693094b..ba00a0fd0 100644
--- a/versioned_docs/version-0.11/docs/introduction/benchmark.md
+++ b/versioned_docs/version-0.11/docs/introduction/benchmark.md
@@ -9,8 +9,8 @@ Different serialization frameworks are suitable for different
scenarios, and ben
If you need to benchmark for your specific scenario, make sure all
serialization frameworks are appropriately configured for that scenario.
Dynamic serialization frameworks supports polymorphism and reference, which
has more cost compared
-to static serialization frameworks, unless it uses the jit techniques as fory
did.
-Since fory will generate code at runtime, please warm up before collecting
benchmark statistics.
+to static serialization frameworks, unless it uses the jit techniques as
Apache Fory™ did.
+Since Apache Fory™ will generate code at runtime, please warm up before
collecting benchmark statistics.
### Java Serialization
diff --git a/versioned_docs/version-0.11/docs/introduction/introduction.md
b/versioned_docs/version-0.11/docs/introduction/introduction.md
index 2d0ce5365..e6672881d 100644
--- a/versioned_docs/version-0.11/docs/introduction/introduction.md
+++ b/versioned_docs/version-0.11/docs/introduction/introduction.md
@@ -4,11 +4,11 @@ title: Introduction
sidebar_position: 1
---
-Fory is a blazing fast multi-language serialization framework powered by
jit(just-in-time compilation) and zero-copy.
+Apache Fory™ is a blazing fast multi-language serialization framework powered
by jit(just-in-time compilation) and zero-copy.
## Protocols
-Different scenarios have different serialization requirements. Fory designed
and implemented
+Different scenarios have different serialization requirements. Apache Fory™
designed and implemented
multiple binary protocols for those requirements:
- Cross-language object graph protocol:
@@ -20,22 +20,22 @@ multiple binary protocols for those requirements:
- Row format protocol: a cache-friendly binary random access format, supports
skipping serialization and partial serialization,
and can convert to column-format automatically.
-New protocols can be added easily based on fory existing buffer, encoding,
meta, codegen and other capabilities. All of those share same codebase, and the
optimization for one protocol
+New protocols can be added easily based on Apache Fory™ existing buffer,
encoding, meta, codegen and other capabilities. All of those share same
codebase, and the optimization for one protocol
can be reused by another protocol.
## Compatibility
### Schema Compatibility
-Fory java object graph serialization support class schema forward/backward
compatibility. The serialization peer and deserialization peer can add/delete
fields independently.
+Apache Fory™ java object graph serialization support class schema
forward/backward compatibility. The serialization peer and deserialization peer
can add/delete fields independently.
We plan to add support cross-language serialization after [meta
compression](https://github.com/apache/fory/issues/203) are finished.
### Binary Compatibility
-We are still improving our protocols, binary compatibility are not ensured
between fory releases for now. Please `shade` fory if you will upgrade fory in
the future.
+We are still improving our protocols, binary compatibility are not ensured
between Apache Fory™ releases for now. Please `shade` Apache Fory™ if you will
upgrade Apache Fory™ in the future.
-Binary compatibility will be ensured before fory 1.0.
+Binary compatibility will be ensured before Apache Fory™ 1.0.
## Security
@@ -43,9 +43,9 @@ Static serialization such as row format are secure by nature.
But dynamic object
For example, the deserialization may invoke `init` constructor or
`equals`/`hashCode` method, if the method body contains malicious code, the
system will be at risks.
-Fory provides a class registration mode option and enabled by default for this
protocol, which allows deserializing trusted registered types or built-in types
only for security.
+Apache Fory™ provides a class registration mode option and enabled by default
for this protocol, which allows deserializing trusted registered types or
built-in types only for security.
-Fory provides a class registration option and enabled by default for such
protocols, which allows only deserializing trusted registered types or built-in
types. **Do not disable class registration or class registration checks unless
you can ensure your environment is indeed secure**. We are not responsible for
security if you disabled the class registration option.
+Apache Fory™ provides a class registration option and enabled by default for
such protocols, which allows only deserializing trusted registered types or
built-in types. **Do not disable class registration or class registration
checks unless you can ensure your environment is indeed secure**. We are not
responsible for security if you disabled the class registration option.
## RoadMap
diff --git a/versioned_docs/version-0.12/docs/introduction/benchmark.md
b/versioned_docs/version-0.12/docs/introduction/benchmark.md
index 37693094b..ba00a0fd0 100644
--- a/versioned_docs/version-0.12/docs/introduction/benchmark.md
+++ b/versioned_docs/version-0.12/docs/introduction/benchmark.md
@@ -9,8 +9,8 @@ Different serialization frameworks are suitable for different
scenarios, and ben
If you need to benchmark for your specific scenario, make sure all
serialization frameworks are appropriately configured for that scenario.
Dynamic serialization frameworks supports polymorphism and reference, which
has more cost compared
-to static serialization frameworks, unless it uses the jit techniques as fory
did.
-Since fory will generate code at runtime, please warm up before collecting
benchmark statistics.
+to static serialization frameworks, unless it uses the jit techniques as
Apache Fory™ did.
+Since Apache Fory™ will generate code at runtime, please warm up before
collecting benchmark statistics.
### Java Serialization
diff --git a/versioned_docs/version-0.12/docs/introduction/introduction.md
b/versioned_docs/version-0.12/docs/introduction/introduction.md
index 2d0ce5365..e6672881d 100644
--- a/versioned_docs/version-0.12/docs/introduction/introduction.md
+++ b/versioned_docs/version-0.12/docs/introduction/introduction.md
@@ -4,11 +4,11 @@ title: Introduction
sidebar_position: 1
---
-Fory is a blazing fast multi-language serialization framework powered by
jit(just-in-time compilation) and zero-copy.
+Apache Fory™ is a blazing fast multi-language serialization framework powered
by jit(just-in-time compilation) and zero-copy.
## Protocols
-Different scenarios have different serialization requirements. Fory designed
and implemented
+Different scenarios have different serialization requirements. Apache Fory™
designed and implemented
multiple binary protocols for those requirements:
- Cross-language object graph protocol:
@@ -20,22 +20,22 @@ multiple binary protocols for those requirements:
- Row format protocol: a cache-friendly binary random access format, supports
skipping serialization and partial serialization,
and can convert to column-format automatically.
-New protocols can be added easily based on fory existing buffer, encoding,
meta, codegen and other capabilities. All of those share same codebase, and the
optimization for one protocol
+New protocols can be added easily based on Apache Fory™ existing buffer,
encoding, meta, codegen and other capabilities. All of those share same
codebase, and the optimization for one protocol
can be reused by another protocol.
## Compatibility
### Schema Compatibility
-Fory java object graph serialization support class schema forward/backward
compatibility. The serialization peer and deserialization peer can add/delete
fields independently.
+Apache Fory™ java object graph serialization support class schema
forward/backward compatibility. The serialization peer and deserialization peer
can add/delete fields independently.
We plan to add support cross-language serialization after [meta
compression](https://github.com/apache/fory/issues/203) are finished.
### Binary Compatibility
-We are still improving our protocols, binary compatibility are not ensured
between fory releases for now. Please `shade` fory if you will upgrade fory in
the future.
+We are still improving our protocols, binary compatibility are not ensured
between Apache Fory™ releases for now. Please `shade` Apache Fory™ if you will
upgrade Apache Fory™ in the future.
-Binary compatibility will be ensured before fory 1.0.
+Binary compatibility will be ensured before Apache Fory™ 1.0.
## Security
@@ -43,9 +43,9 @@ Static serialization such as row format are secure by nature.
But dynamic object
For example, the deserialization may invoke `init` constructor or
`equals`/`hashCode` method, if the method body contains malicious code, the
system will be at risks.
-Fory provides a class registration mode option and enabled by default for this
protocol, which allows deserializing trusted registered types or built-in types
only for security.
+Apache Fory™ provides a class registration mode option and enabled by default
for this protocol, which allows deserializing trusted registered types or
built-in types only for security.
-Fory provides a class registration option and enabled by default for such
protocols, which allows only deserializing trusted registered types or built-in
types. **Do not disable class registration or class registration checks unless
you can ensure your environment is indeed secure**. We are not responsible for
security if you disabled the class registration option.
+Apache Fory™ provides a class registration option and enabled by default for
such protocols, which allows only deserializing trusted registered types or
built-in types. **Do not disable class registration or class registration
checks unless you can ensure your environment is indeed secure**. We are not
responsible for security if you disabled the class registration option.
## RoadMap
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
