...
Note that most modern browsers limit the maximum number of simultaneous HTTP connections. Thus, if you show a lot of renditions simultaneously (e.g., thumbnails in an asset list), strongly consider using the mode argument to limit the number of simultaneous HTTP connections. Please be careful that you do not cache the fallback image as the requested image.
In rare cases, the generation of a rendition might fail. In the old transcode system, an asset streamer URL would not be returned in this case. In the new transcode system, an asset streamer URL is returned in this case, but the asset streamer request returns an HTTP 500 error. A fallback image is never returned by the asset streamer when the generation of the requested generation has failed. Please consider showing a fallback image to end users if an HTTP 500 error is returned.
If you are using the SDK, be aware that the default HTTP client used by the SDK has a timeout of 100 seconds. Thus, if you request a rendition that takes more than 100 seconds to become available with the INewAssetStreamerService.GetAssetDownloadStream method, your request will time out before the rendition is returned. To disable this timeout, use the following setup in your application startup logic:
...