Introduction
This article provides an overview of the two options an application, a service, or an Intuiface experience can use to communicate with a separate Intuiface experience.
The option you choose will depend on the operating system on which the sending or receiving Intuiface experience is running.
- Local Network Triggers: Use if your deployment is on a closed network and requires communication over a LAN. The receiver Intuiface Player must be running on a Windows PC.
- Web Triggers: Use if your deployment has internet access, or if the sender is not on the same network as the receiver. For example, an end-user mobile phone sending commands to an Intuiface experience. The receiver Intuiface Player can run on any Player-supported operating system.
Receive a message in an Intuiface Experience
The table below shows which option can be used based on which OS the receiver Intuiface Player is running.
Local Network Triggers |
YES |
NO |
Web Triggers |
YES |
YES |
Send a message from an Intuiface Experience
Sending information via Local Network Triggers or Web Triggers can be performed by any application or service using Intuiface's HTTP APIs. In addition, Intuiface experiences can natively use either approach to send messages.
The table below breaks down the different methods to send such messages, based on the sender Intuiface Player's OS.
Local Network Triggers |
YES
|
YES
|
YES
|
Web Triggers |
YES
|
YES
|
YES
|
Video explanation - Experience-to-experience communication
You will find the the Quarterly Q&A Live - Fall edition 2022 video, a detailed example on how to send messages between running experiences.
Comments
0 comments
Article is closed for comments.