...
- New version of the content-player should support for the old contents(Unstreamed mp4 contents).
- Newley created streaming content should not visible in the old version of content-player
Solution 1: Content Meta Data should have streaming video config
For the newly created content meta should have config for the video streaming so latest version of content player will stream the video based on the config in metadata.
| Code Block |
|---|
metaData={
videoStreaming:true
} |
Based on the config the content-player will stream the video contents.
Pros:
...
1.Old contents still will play as it is. will not going to break the contract.
Cons:
1.To identify the streaming url the platform as to send extra property
Solution 2: New streaming mime type content
Currently content-player supports the below video mime type contents all these mime type contents are launched by org.ekestep.videorenderer-1.0 plugin.
...
- Need to maintain the multiple version of video js library.
Solution
...
3: Content Migration
Migrate all mp4/webm contents to streaming format so then new version of content-player will play the contents without breaking the contract.
...
2. The contents which is already downloaded in the mobile will not be going to play in the new version content-player.
Solution
...
4: Content player Should detect the streaming url.
The content player should find weather is mp4/web/streaming url with the help of the asset extension.
Sample streaming url link: http://sunbirdspikemedia-inct.streaming.media.azure.net/afcc5a99-d0c4-4ef5-9dfe-dc403a1269fb/learn-colors-with-numbers-in-kid.ism/manifest(format=m3u8-aapl-v3)
Example:
1. sample_video.mp4 -→ Mp4 video content.
...