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 2b90fad60 🔄 synced local 'docs/specification/' with remote
'docs/specification/'
2b90fad60 is described below
commit 2b90fad60098088748a02d0cccbb4e1c7cfbe86d
Author: chaokunyang <[email protected]>
AuthorDate: Tue Sep 23 02:28:09 2025 +0000
🔄 synced local 'docs/specification/' with remote 'docs/specification/'
---
docs/specification/java_serialization_spec.md | 8 ++++----
docs/specification/xlang_serialization_spec.md | 10 +++++-----
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/docs/specification/java_serialization_spec.md
b/docs/specification/java_serialization_spec.md
index 283bc3078..dd2f57cce 100644
--- a/docs/specification/java_serialization_spec.md
+++ b/docs/specification/java_serialization_spec.md
@@ -392,8 +392,8 @@ which will be encoded by elements header, each use one bit:
- If track elements ref, use the first bit `0b1` of the header to flag it.
- If the collection has null, use the second bit `0b10` of the header to flag
it. If ref tracking is enabled for this
element type, this flag is invalid.
-- If the collection element types are not declared type, use the 3rd bit
`0b100` of the header to flag it.
-- If the collection element types are different, use the 4th bit `0b1000`
header to flag it.
+- If the collection element types are the declared type, use the 3rd bit
`0b100` of the header to flag it.
+- If the collection element types are same, use the 4th bit `0b1000` header to
flag it.
By default, all bits are unset, which means all elements won't track ref, all
elements are same type, not null and
the actual element is the declared type in the custom class field.
@@ -459,11 +459,11 @@ KV header:
- If track key ref, use the first bit `0b1` of the header to flag it.
- If the key has null, use the second bit `0b10` of the header to flag it. If
ref tracking is enabled for this
key type, this flag is invalid.
-- If the actual key type of map is not the declared key type, use the 3rd bit
`0b100` of the header to flag it.
+- If the actual key type of map is the declared key type, use the 3rd bit
`0b100` of the header to flag it.
- If track value ref, use the 4th bit `0b1000` of the header to flag it.
- If the value has null, use the 5th bit `0b10000` of the header to flag it.
If ref tracking is enabled for this
value type, this flag is invalid.
-- If the value type of map is not the declared value type, use the 6rd bit
`0b100000` of the header to flag it.
+- If the value type of map is the declared value type, use the 6rd bit
`0b100000` of the header to flag it.
- If key or value is null, that key and value will be written as a separate
chunk, and chunk size writing will be
skipped too.
diff --git a/docs/specification/xlang_serialization_spec.md
b/docs/specification/xlang_serialization_spec.md
index 83719872c..d44590c37 100644
--- a/docs/specification/xlang_serialization_spec.md
+++ b/docs/specification/xlang_serialization_spec.md
@@ -597,7 +597,7 @@ Which encoding to choose:
- If the string is encoded by `utf-8`, then fory will use `utf-8` to decode
the data. Cross-language string
serialization of fory uses `utf-8` by default.
-### list
+### collection/list
Format:
@@ -614,8 +614,8 @@ which will be encoded by elements header, each use one bit:
- If track elements ref, use the first bit `0b1` of the header to flag it.
- If the elements have null, use the second bit `0b10` of the header to flag
it. If ref tracking is enabled for this
element type, this flag is invalid.
-- If the element types are not the declared type, use the 3rd bit `0b100` of
the header to flag it.
-- If the element types are different, use the 4th bit `0b1000` header to flag
it.
+- If the element types are the declared type, use the 3rd bit `0b100` of the
header to flag it.
+- If the element types are smae, use the 4th bit `0b1000` header to flag it.
By default, all bits are unset, which means all elements won't track ref, all
elements are same type, not null and
the actual element is the declared type in the custom type field.
@@ -718,11 +718,11 @@ KV header:
- If track key ref, use the first bit `0b1` of the header to flag it.
- If the key has null, use the second bit `0b10` of the header to flag it. If
ref tracking is enabled for this
key type, this flag is invalid.
-- If the actual key type of map is not the declared key type, use the 3rd bit
`0b100` of the header to flag it.
+- If the actual key type of map is the declared key type, use the 3rd bit
`0b100` of the header to flag it.
- If track value ref, use the 4th bit `0b1000` of the header to flag it.
- If the value has null, use the 5th bit `0b10000` of the header to flag it.
If ref tracking is enabled for this
value type, this flag is invalid.
-- If the value type of map is not the declared value type, use the 6rd bit
`0b100000` of the header to flag it.
+- If the value type of map is the declared value type, use the 6rd bit
`0b100000` of the header to flag it.
- If key or value is null, that key and value will be written as a separate
chunk, and chunk size writing will be
skipped too.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
