Common timeline processing for unique manifests

A non-transitory memory storing one or more programs, which, when executed by one or more processors of one or more servers with one or more network interfaces, cause the one or more servers to:

• generate manifest data in an object store while recording data for a plurality of clients, wherein the object store stores the manifest data corresponding to the recorded data in different common manifest files corresponding to predefined durations without tracking a plurality of recording identifiers (IDs) for the plurality of clients in the different common manifest files;
• generate and store manifest files in a cache outside an object store in response to receiving playback requests from the plurality of clients, wherein the manifest files are shared by the plurality of clients, and the manifest files are stored in the cache according to the predefined durations along recording timelines, including:
• receiving a request from a client for a unique manifest, wherein the request indicates a recording timeline and includes a recording ID;
• determining whether a corresponding portion of the recording timeline exists in the cache;
• in accordance with determining that the corresponding portion of the recording timeline exists in the cache, obtaining from the cache one or more manifest files according to the corresponding portion of the recording timeline and constructing at least a portion of the unique manifest using the one or more manifest files,
• in accordance with determining that the corresponding portion of the recording timeline does not exist in the cache, obtaining from the object store a set of the different common manifest files corresponding to the recording timeline and constructing at least the portion of the unique manifest using the set of the different common manifest files;
• modifying the unique manifest by appending the recording ID of the request to a URL prefix in the unique manifest;
• and
• storing the unique manifest in the cache according to the predefined duration along the recording timeline;
• and
• send the unique manifest to the client.

A device comprising:

• one or more processors;
• one or more non-transitory memory;
• one or more network interfaces;
• and
• one or more programs, stored in the one or more non-transitory memory, which, when executed by the one or more processors, cause the device to:
• generate manifest data in an object store while recording data for a plurality of clients, wherein the object store stores the manifest data corresponding to the recorded data in different common manifest files corresponding to predefined durations without tracking a plurality of recording identifiers (IDs) for the plurality of clients in the different common manifest files;
• generate and store manifest files in a cache outside an object store in response to receiving playback requests from the plurality of clients, wherein the manifest files are shared by the plurality of clients, and the manifest files are stored in the cache according to the predefined durations along recording timelines, including:
• receiving a request from a client for a unique manifest, wherein the request indicates a recording timeline and includes a recording ID;
• determining whether a corresponding portion of the recording timeline exists in the cache;
• in accordance with determining that the corresponding portion of the recording timeline exists in the cache, obtaining from the cache one or more manifest files according to the corresponding portion of the recording timeline and constructing at least a portion of the unique manifest using the one or more manifest files,
• in accordance with determining that the corresponding portion of the recording timeline does not exist in the cache, obtaining from the object store a set of the different common manifest files corresponding to the recording timeline and constructing at least the portion of the unique manifest using the set of the different common manifest files;
• modifying the unique manifest by appending the recording ID of the request to a URL prefix in the unique manifest;
• and
• storing the unique manifest in the cache according to the predefined duration along the recording timeline;
• and
• send the unique manifest to the client.