Replies: 1 comment 1 reply
-
For v1 we once started to writing something here: https://tauri.app/v1/references/architecture/inter-process-communication/#commands it's pretty basic but the v1 ipc itself is pretty basic itself. The OS is not involved, the webviews just offer "postMessage()" apis we use to pass the messages, but in v1 serializing everything to json strings is indeed required. The new ipc in v2 is a mix between the old one and custom protocols (basically http/network requests with fetch that don't actually hit the network). This is faster and more flexible (for example it allow binary payloads) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm starting to do some Tauri development and I was reading through the docs, specifically the Calling Rust from the frontend work. And I was just curious how does it actually work? Does it serialize the call from JS to JSON? Does it work via OS IPC? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions