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 47e97055 🔄 synced local 'docs/guide/' with remote 'docs/guide/'
47e97055 is described below
commit 47e9705592e4b4fe4740c861ad13f8648021380d
Author: chaokunyang <[email protected]>
AuthorDate: Mon Jun 23 13:46:04 2025 +0000
🔄 synced local 'docs/guide/' with remote 'docs/guide/'
---
docs/guide/java_serialization_guide.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/guide/java_serialization_guide.md
b/docs/guide/java_serialization_guide.md
index bd0e14a8..14e9134c 100644
--- a/docs/guide/java_serialization_guide.md
+++ b/docs/guide/java_serialization_guide.md
@@ -177,8 +177,8 @@ byte[] bytes = fory.serialize(object);
System.out.println(fory.deserialize(bytes));
```
-Note that calling `buildThreadSafeFory()` on `ForyBuilder` will create an
instance of `ThreadLocalFory`.
-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.
+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 fory instance, a relatively expensive operation.
An alternative for virtual threads is to use `buildThreadSafeForyPool`.
### Handling Class Schema Evolution in Serialization
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
