Static Resources¶

Introduction¶

The server is also responsible to serve some static resources for the clients.
This document presents the URL schemes used to serve those static resources.

In those URL schemes, the following variables can be used:

• <server_url>

Represents the ROOT URL of the server. For instance http://stagingapi.familywall.com

• <PARTNER>

Represents a variable indicating for which partner the resource shall be queried. Normally for the generic, unbranded, uncustomized version you shall use 'generic'. If partner is used such as htc, its value is defined by an API ENUM and it is uppercase.

• <country_code>

Represents a country code as per https://en.wikipedia.org/wiki/ISO_3166-1 alpha2 , so it is uppercase. There is also a 'default' value in lowercase available.

• <locale>

Represents a locale code with the <lowercase-locale>-<underscore>-<uppercase-locale> java syntax. There is also a 'default' value in lowercase available.

Terms&Condition files¶

Terms&Condition texts are served as a simple html document (no style).

<server_url>/legal/<PARTNER>/legal/<country_code>/terms.html

Avatar and Blasons¶

Avatar are served as png files in <server_url>/avatar

Family blasons are served as png files in <server_url>shield

In order to same memory on the server's filer, those urls must be used when using avatar and shield for family profile and account profile.

Those resources must be upgraded in order to have a real specified list and a way to have different resources depending on the partner.