Note: this page is inspired by (and often copied verbatim from) the original fourth lesson, Lesson: Pico to Pico Subscriptions.
After completing this lesson, you will be able to do the following:
You should have already completed the following lessons:
node pico-engine quickstart lesson. (Be able to register and install rulesets)
Lesson 1. events and queries. (Be able to create channels and understand how events are raised on channels)
Lesson 3. Pico-based systems. (Be able to manage the pico lifecycle using UI and programmatically)
Subscriptions play an important role in building systems of picos. In Lesson 3. Pico-based systems, you created child picos. If the parent-child relationship were the only one that existed, we could create hierarchies of picos, but not peer-to-peer systems of picos. Subscriptions allow us to establish relationships between any two picos.
A subscription represents a relationship between two picos. It has a name and two channels, one from each pico participating in the subscription to the other. Each side in the subscription can be given a role to further identify the purpose of the subscription.
To be written...
Wrangler provides functions, actions, and rules for managing subscriptions from within your KRL code.