Ability to define a ResourceFile URL for SmallThumbnail, Thumbnail, and Preview.

Who would benefit?

Anyone who uses an external CDN.

What impact would it make?

It would remove the need to use a proxy to re-direct urls ending in /SmallThumbnail, /Thumbnail, and /Preview. This will remove unnecessary complexity and additional costs for customers.

How should it work?

I have 2 proposed solutions. One is simple and the other is more complicated, but offers more flexibility.

Solution #1: In the ResourceFile object, add 3 new fields (SmallThumbnailUrl, ThumbnailUrl, and PreviewUrl). If these fields are filled out, instead of appending /SmallThumbnail at the end of the URL, get the small thumbnail from the SmallThumbnailUrl field instead. Apply the same logic for the other url fields.

Solution #2: Create a new extension type or template for rendering the SmallThumbnail, Thumbnail, or Preview for resources. Extension/template should have access to all of the Resource entity fields, and would allow customers to define the logic for retrieving/generating resource previews.

Why is it needed?

The current way to render resource previews from external CDNs requires some type of proxy if it does not support /SmallThumbnail, /Thumbnail, or /Preview at the end of the URL. It offers no control on how these thumbnails or previews should be rendered. More control is needed so that external CDNs can be properly supported.