mirrors/leptos-book
1
0
Fork 0
mirror of https://github.com/leptos-rs/book.git synced 2025-12-27 11:06:43 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update working_with_signals.md broken link to server-side rendering (#216)

Browse Source 
the original link "../ssr/README.md" shows 
"Document not found (404)
This URL is invalid, sorry. Please use the navigation bar or search to continue."
I think the corrected one should be "../ssr/" to show this page
"Part 2: Server Side Rendering"
This commit is contained in:
Abdelrahman Omar
2025-08-19 04:39:16 +03:00
committed by GitHub
parent 16c53319a4
commit ec54e24169
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/reactivity/working_with_signals.md
View File

@@ -62,7 +62,7 @@ Now our function simply takes `names` by reference to run `is_empty()`, avoiding
## Thread Safety and Thread-Local Values ## Thread Safety and Thread-Local Values
You may have noticed, either by reading the docs or by experimenting with your own applications, that the values that are stored in signals must be `Send + Sync`. This is because the reactive system actually supports multi-threading: signals can be sent across threads, and the whole reactive graph can work across multiple threads. (This is especially useful when doing [server-side rendering](../ssr/README.md) with server frameworks like Axum, which use Tokio’s multi-threaded executor.) In most cases, this has no effect on what you do: ordinary Rust data types are `Send + Sync` by default. You may have noticed, either by reading the docs or by experimenting with your own applications, that the values that are stored in signals must be `Send + Sync`. This is because the reactive system actually supports multi-threading: signals can be sent across threads, and the whole reactive graph can work across multiple threads. (This is especially useful when doing [server-side rendering](../ssr/) with server frameworks like Axum, which use Tokio’s multi-threaded executor.) In most cases, this has no effect on what you do: ordinary Rust data types are `Send + Sync` by default.
However, the browser environment is only single-threaded unless you use a Web Worker, and the JavaScript types provided by `wasm-bindgen` and `web-sys` are all explicitly `!Send`. This mean they can’t be stored in ordinary signals. However, the browser environment is only single-threaded unless you use a Web Worker, and the JavaScript types provided by `wasm-bindgen` and `web-sys` are all explicitly `!Send`. This mean they can’t be stored in ordinary signals.