Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support maxwidth/maxheight constraints #58

Open
jonnor opened this issue Feb 9, 2016 · 0 comments
Open

Support maxwidth/maxheight constraints #58

jonnor opened this issue Feb 9, 2016 · 0 comments

Comments

@jonnor
Copy link
Member

jonnor commented Feb 9, 2016

Right now we have universal height/width support, with possibility of specifying only one of these and original aspect ratio will be used. However, on images with very wide/tall aspect ratios this can be far from what UIs expect.
One strategy used is to say, give me an image where height is up to N and width is up to N.

Also, the semantics of height/width is to provide exactly the dimensions specified, making it not possible for us to return cached (already processed) very-similar-but-not-100% over.
A challenge is that currently we do assume a 1-to-1 mapping of request parameters and an output image. With loose constraints like this, there is a large number of outputs possible.

This can potentially help in consolidating image sizes requested by clients, which reduces costs, and improves responsiveness for users due to higher cache hit ratios.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant