You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 21, 2024. It is now read-only.
Hello, and thank you for your issue. Could your or @temparus please provide some more details on the requirements and usecases?
It seems to me that this is mostly needed as a feature to send less data, correct? If I correctly recall a conversation with @temparus, this is intended to allow posters to be uploaded in large size for print, while automatically being downscaled for web view?
If this is correct, I would propose simply adding a automatically populated field (image)_compressed, e.g. img_poster_compressed:
The *_compressed field would be read-only.
When uploading an image, the API automatically computes a down-scaled version and stores it alongside the high resolution image.
When requesting the images, clients can decide whether to use the link from e.g. img_poster or img_poster_compressed
This solution would be very simple to implement and not require any new resources, query parameters, etc.
However, I cannot tell if it would fit the requirements -- it would be great if you could provide some more details. Thanks!
As discussed with @temparus: A nice enhancement would be if the api would scale the images automatically to the expected ratio
The text was updated successfully, but these errors were encountered: