Skip to content

Commit 1d8ec58

Browse files
committed
mention that events use commands internally
This is important to mention to make it clear to the developer what they need to do to secure their application.
1 parent b75602a commit 1d8ec58

File tree

1 file changed

+6
-0
lines changed
  • src/content/docs/concept/Inter-Process Communication

1 file changed

+6
-0
lines changed

src/content/docs/concept/Inter-Process Communication/index.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,12 @@ Core -> Frontend: "Event"{style.animated: true}
5454
<figcaption>Events sent between the Core and the Webview.</figcaption>
5555
</figure>
5656

57+
<!-- This is important to mention to make it clear to the developer
58+
what they need to do to secure their application. -->
59+
Under the hood, events still utilize Commands,
60+
and the access to the events API is controlled by the
61+
[Event permissions](/reference/acl/core-permissions/#event).
62+
5763
## Commands
5864

5965
Tauri also provides a [foreign function interface]-like abstraction on top of IPC messages[^1]. The primary API, `invoke`, is similar to the browser's `fetch` API and allows the Frontend to invoke Rust functions, pass arguments, and receive data.

0 commit comments

Comments
 (0)