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 9a84e4db 🔄 synced local 'docs/guide/' with remote 'docs/guide/'
9a84e4db is described below
commit 9a84e4dbe42172efbdc136dd3ae7c0e3fad33d9a
Author: chaokunyang <[email protected]>
AuthorDate: Fri Jun 20 01:59:32 2025 +0000
🔄 synced local 'docs/guide/' with remote 'docs/guide/'
---
docs/guide/java_serialization_guide.md | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/docs/guide/java_serialization_guide.md
b/docs/guide/java_serialization_guide.md
index df142ceb..5af400e4 100644
--- a/docs/guide/java_serialization_guide.md
+++ b/docs/guide/java_serialization_guide.md
@@ -177,6 +177,10 @@ byte[] bytes = fory.serialize(object);
System.out.println(fory.deserialize(bytes));
```
+Note that calling `buildThreadSafeFory()` on `ForyBuilder` will create an
instance of `ThreadLocalFury`.
+This may not be appropriate in environments where virtual threads are used, as
each thread will create its own fury instance, a relatively expensive operation.
+An alternative for virtual threads is to use `buildThreadSafeForyPool`.
+
### Handling Class Schema Evolution in Serialization
In many systems, the schema of a class used for serialization may change over
time. For instance, fields within a class
@@ -1232,6 +1236,9 @@ Object newObj = fory.execute(
);
```
+Note that `MetaContext` is not thread-safe and cannot be reused across
instances of fory or multiple threads.
+In cases of multi-threading, a separate `MetaContext` must be created for each
fory instance.
+
### Deserialize non-existent classes
Fory support deserializing non-existent classes, this feature can be enabled
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
