Tightly Coupled Interaction for Custom Apps
With tightly-coupled interactions, both publisher and subscriber apps know the topic name involved in an interaction and the topic payload for that type of event. Generally, both apps must be developed together to sustain tightly-coupled interactions.
In most cases, the apps involved in a tightly-coupled interaction are all custom apps. Basic apps created in the App Maker wizard can be used as publishers in a tightly-coupled interaction, but they cannot be subscribers.
There are two requirements to implement a tightly-coupled interaction:
Bundle the tightly-coupled apps together for end use in either:
A workspace app created in
Mashboard.
Simply create a new workspace in
Mashboard (see
Create Workspace Apps with
Mashboard for instructions). Then add the tightly-coupled apps to the workspace or to one tab or page of a multi-tab or multi-page workspace.
No wiring is needed to enabled interactions between tightly-coupled apps that are bundled within a workspace app.
Save the workspace app. You can then publish the workspace to the AppDepot or publish or embed the workspace in other destinations to allow you and other users to use the tightly-coupled apps.
External HTML pages.
You can simply directly embed each app involved in a tightly-coupled interaction in any HTML page using
<script> tags. You must use specific parameters in the
<script> tags in this case. See
Embedding Tightly Coupled Apps for details.
Subscribers can also use
Wildcard Subscriptions for Tightly-Coupled Interactions to subscribe to a set of topics.
Note: | For links to other app examples, click  More... above. |
