Content Streams, Objects & Blobs

the nativewaves content service utilizes the concepts of content streams, objects, and blobs to manage stored content effectively, such as video files the service utilizes common content formats for video, audio and data and provides interfaces where the content can be uploaded here's an explanation of each concept content streams they serve as containers for multiple content objects, providing a structured organization for related content objects content streams imply a time relationship between the objects they contain for example, if two content objects exist simultaneously within a content stream (based on their detected content start time), it suggests that both objects hold the same content this makes it easy to achieve full end to end redundancy because if a content object ends then a system can easily switch to another object within the content stream content objects content objects reside within content streams and can encompass multiple content blobs they represent logical entities that group together content blobs that store content in different formats content blobs content blobs are the units that actually hold the stored content data they are bound to a content format, e g for video mp4, hls, and represent a distinct piece of content they also specify in which content store the content is stored the content stream, object & blobs concept is primarily used in the smep service docid\ bahfu3fbshk0ctqauif9e for handling nativewaves exp docid\ dbafnw1 h6cu4q qhzprm events, as it simplifies the management of live scenarios, facilitating content synchronization, format handling and adaptability to changes in an event timeline