| Table of Contents | ||
|---|---|---|
|
...
| Warning | ||
|---|---|---|
| ||
The rule that reacts to a |
Subscriptions also provides an API event that the KRL developer can raise to send an event on a subscription. The developer can choose to either send an event to a specific subscription ID, to all subscriptions with a certain Tx_role, or all subscriptions with a certain Rx_role, or a mixture of the three.
...
The ID of a subscription identifies a subscription relationship. By default it is a globally unique identifier assigned by wrangler, but it can be set by the developer in the initial wrangler:subscription event. Both picos record the same ID for the subscription, as the ID represents the relationship itself.
...
| Info | ||
|---|---|---|
| ||
This section is solely for illustrating how the protocol works under-the-hood. The internal events used are not static and are subject to change, and should not be selected on for long-term code. For public, reliable API events see Subscriptions API. |
Subscription Creation
To establish a basic subscription between pico A and pico B:
...
2. Pico A sends pico B wrangler:new_subscription_request. Pico A sends all attributes it received in wrangler:subscription with the following key attributes updated:
...