Skip to Content

Data Binding - Introduction

Printer-friendly versionSend to friendPDF version
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

Those capabilities will take place at different levels in service architecture, and will manage data of different natures:

 

Rich Media content

Some of those capabilities are dealing with Rich Media scenes, meaning the data that will be displayed by Streamezzo Rich Media Client (RMC). Those scenes are already processed, and may be cached.

This can be client side cache, for instant access to a server-side scene while it has been already access by the end user:

 

 

Or server side cache (Level 1 cache), for instant response if the scene has been processed previously, for example by another end user:

 

Rich Media scenes also may be used to enrich current graphical interface instead of replacing it (append mode). This will allow minimizing the amount of data to be received from the Rich Media Server (RMS):

 

External data

Some of those capabilities are dealing with data that will be used to compose your scenes at processing time.

This can be data retrieve from any back end, using dedicated connector:

 

Or this can be any kind of other external resources.

Both will be able to take advantage of server-side caching capabilities of RMS:

 

For example, in a case of a Mobile TV application, you could imagine an EPG (Electronic Program Guide) with daily data (program images, textual descriptions, date, duration, etc…) retrieved form a back-end server, and channel logos download thru HTTP from a distant server.

File transfer

Then, some of those capabilities are dealing with the files you would like to share between your server-side platform and your end user's devices (client side), other than Rich Media scenes description.
Those files may be of any format you want, if it makes sense to you to hold it on device.

 

In few words, the file uploads, from device to server, will be managed between the RMC and the Upload Server.

The file downloads will be managed by the RMC, while the targeted files can be hosted on whatever server.

Thanks to your dedicated connector, you will be able to receive from or send to a given back-end or whatever external API you plan to use on your platform.

Share this