The mechanism used to download and store media can vary based on the licensing approach chosen. Here is a summary of when data is downloaded for the experience and for the Headless CMS (H-CMS).
|Headless CMS||Manifest +
|Deploy & Sync-request||Launch & Sync-request||Launch & Sync-request|
|Media||Deploy & Sync-request||Launch & Sync-request||Web request|
|Video||Deploy & Sync-request||Launch & Sync-request||Progressive download|
Understanding the table
- .ifx: This is the project file created by Composer. It's the heart of a project. Never edit it by hand!
- Media: All Intuiface asset types other than videos.
- Manifest: H-CMS base(s) used by the experience.
- Long Text: Unlike short text, which is stored in the manifest, long text is retrieved separately.
- Deploy: Downloaded when the experience is deployed. Deployment is incomplete until all media across the entire experience (and thus across all scenes) is downloaded in its entirety. The experience cannot be run until the deployment has finished.
- Launch: When the experience URL is loaded in a web browser or when the PWA is run. The webpage/PWA is not entirely loaded until all associated files are downloaded in their entirety. The webpage/PWA will not run until all downloading has been completed.
- Web request: Media is downloaded only when that media is visible onscreen. Once loaded, the associated browser's cache mechanism determines if it will be downloaded again or if a cached copy will be used when the media goes offscreen and then returns.
- Progressive download: Like a web request, but the video will play immediately - rather than waiting for the entire file to be downloaded - and can be paused, rewound, etc. Video caching is determined by the browser and may or may not occur. If not cached, the video will be progressively downloaded every time it is played. Internet connectivity is required.
- Sync-request: Specific to the Headless CMS, this is the synchronization mechanism that keeps the local copy of the H-CMS base in sync with the online master. Synchronization always occurs at experience launch and can be initiated by the experience at any time.
Performance tradeoffs of Player Licensing vs. Views Licensing
For in-venue deployments, PWA deployments, and webpage deployment with Player Licensing:
- All media is downloaded before the first run. The initial run is delayed until all downloads have been completed, but offline use is possible, and performance is unaffected by network speeds.
For webpage deployments with Views Licensing:
- Views licensing enables near-instant use of the running experience but requires internet connectivity at all times and thus may suffer performance issues if the network is slow or if very large media files are part of the experience.