Skip to Content

How to take advantage of caching facilities

Printer-friendly versionSend to friendPDF version
Intermediate
This tutorial explains how to store rich media data in cache, granting a more immediate access to such content while it remains valid, and thus improving the user experience by reducing latency.
Such data can be stored on the device itself, i.e. in client cache, once processed and delivered by Streamezzo Rich Media Server, for an instantaneous and offline access.
Server cache mechanism is also available in order to make it possible to deliver a content to the client more rapidly.

Principle

Streamezzo framework provides straightforward facilities to cache content either locally on device (instant and offline access to this content for the end-user) or remotely on server (improved delivery time to multiple devices).

Some advanced facilities are also granted for fine cache management.

Combining both client and server side caching grants a faster access to and faster delivery of rich media content.

Client-side cache

On client-side, a rich media content (scene) data delivered by Streamezzo Rich Media Server can be:

  • stored in cache, i.e. the currently requested and downloaded scene is rendered and stored in client cache simultaneously, so that the next access to this scene will be immediate (as long as this content has not reached a specified expiration time)
  • prefetched in cache, i.e. the currently requested and downloaded scene also comes with data from other scene(s) that are stored in client cache, so the access to this/those scene(s) will be immediate (as long as this content has not reached a specified expiration time)

Connection can also be managed in order to download additional scenes data in cache as soon as the connection becomes available (optimized connection usage). This is performed in background, without interfering with the application usage, queuing the list of scene to be downloaded and store in cache when possible.

The client-side caching facilities are detailed in this tutorial.

Server-side cache

On server-side, 2 cache levels can be exploited with advantage:

  • processed scenes caching (level 1), i.e. the currently processed scene result is delivered to requesting client and is also stored in server cache, so that next clients requesting the same content can have it delivered immediately, without any processing delay (as long as this content has not reached a specified expiration time)
  • external resources caching (level 2), i.e. the distant resources (media) required for the currently requested scene processing can be stored in server cache, so that the next processing delay will be reduced accordingly, getting rid of the external resources download delay (as long as they have not reached a specified expiration time)

The server-side caching facilities are detailed in this tutorial.

Share this