Skip to Content

Data Binding

Rookie

In this section we will give a specific focus on all key aspects related to data binding (storage and exchange), i.e. dealing with Rich Media content, file exchanges and back-ends integration.

Such data management covers the following capabilities:

  • Rich media content client-side caching (on device)
  • Processed rich media content server-side caching
  • Rich media content incremental update (append)
  • Server-side integration with back-ends (connectors)
  • External resources (used for rich media content processing) server-side caching
  • File download from server to device
  • File upload from device to server
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 indeed 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.
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.
Server cache mechanism is indeed available in order to make it possible to deliver a content to the client more rapidly, by sorting processed content or external resources.
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.