Introduction

This document aims to briefly explain the process of migrating to the v3 EPG endpoints.

NB:  Please see API guidelines for app development#EPG for guidelines on the new functionality.  This document does not repeat information contained there

Explanation of differences

The chief difference between v2 and v3 lies in improvements in our caching strategy.

One endpoint is cheap because it can be publicly cached and the other is more expensive because it is unique to a particular user.

The impact on clients is that instead of calling a single endpoint to obtain EPG there are now two endpoints.

• Use the public (cheap) endpoint to display a general EPG
• Use the private (expensive) endpoint to discover the users individual privileges (e.g.: record, catchup, restart) for a particular channel

Model client implementation

This diagram is taken from Caching of EPG data

Concrete examples

Displaying a list of channels

Call

UI example

Playing a specific channel