Skip to content

Commit

Permalink
Merge branch 'feat/guide/app-structure-zome-functions' of github.com:…
Browse files Browse the repository at this point in the history
…holochain/docs-pages into feat/guide/app-structure-zome-functions
  • Loading branch information
pdaoust committed Feb 3, 2025
2 parents b671529 + ff25cda commit 9523efb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/pages/build/callbacks-and-lifecycle-hooks.md
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,7 @@ pub fn init(_: ()) -> ExternResult<InitCallbackResult> {

<!-- TODO: move this to the signals page after it's written -->

Agents in a network can send messages to each other via [remote signals](/concepts/9_signals/#remote-signals). In order to handle these signals, your coordinator zome needs to define a `recv_remote_signal` callback. Remote signals get routed from the emitting coordinator zome on the sender's machine to one of the same name on the receiver's machine.
Agents in a network can send messages to each other via [remote signals](/concepts/9_signals/#remote-signals). In order to handle these signals, your coordinator zome needs to define a `recv_remote_signal` callback. Remote signals get routed from the emitting coordinator zome on the sender's machine to a coordinator with the same name on the receiver's machine.

`recv_remote_signal` takes a single argument of any type you like --- if your coordinator zome deals with multiple message types, consider creating an enum for all of them. It must return an empty `ExternResult<()>`, as this callback is not called as a result of direct interaction from the local agent and has nowhere to pass a return value.

Expand Down

0 comments on commit 9523efb

Please sign in to comment.