...
Both methods end up running the same code and hence are equally good. There are some theoretical advantages of using the HttpHandler as that one is earlier in the .net pipeline and therefore utilizes the IIS better. The disadvantage to this is that the extension of what is requested needs to be known beforehand and as such, this is not always doable.
Using HttpHandler
As the download and stream are implemented as a HttpHandler, it is a bit different than the other endpoints. The URL can be constructed in the following way
...
| Name | Description |
|---|---|
| assetid | This is the id of the asset in Digizuite |
| mediaformatid | The format in which the asset is transcoded is defined in Digizuite. This id corresponds to such a format |
| destinationid | This implies where the file should be downloaded from. These IDs are accessible in Digizuite under System tools/Destinations |
| assetype | Determines the type of the asset. Use GetAssetTypes to get a list of all available asset types |
| outputident | Enum that determines how the file should be output. 11 is default preview (used for stream) and 44 is download |
| filmstripid | Is there for backward compatibility - i.e. it's not used anymore. Set this to 0. |
| accessKey | The accessKey that grants access to the api |
| Download boolean | True = file downloaded and False = file is returned as a stream |
| Extension of mediaformat | This should be set to whatever the mediaformat is setup to create (i.e. jpg, if the output of the format is a jpg file) |
Using aspx
The apsx URL can be constructed in the following manner:
...