I’ve observed video content returned as byte array(ComplexData) for the API shown in below screenshot. Find the data size is 15 MB.
The video is displayed with video URL as shown below.
It means the byte array which was returned from the previous API is not being used here.
Since video content is being traveled through the network, it is causing delayed load time of dashboards where video size is >100MB and sometimes page load errors occur.
From API perspective it looks complete but shall we extend the following api to skip video/image(ComplextData) content so that the API will load faster?
Or any other better way for the faster load? Returning whole video content from API is very costly.