New changes (“v” : 1.20)
In previous versions of Blitline, we have taken the ‘smaller’ is better approach to default values and opted to minimize the size of images. In the latest “v”ersion of Blitline, we are going to change one of the default values.
Previously we have defaulted to stripping out all metadata and color profiles. We, going forward, are going to automatically strip metadata but KEEP color profile information. You will need to ‘opt out’ of saving color profile information IF you are using “v”ersion 1.20 or higher for Blitline JSON.
Many people don’t even know we offer different “v”ersions. You can set the version by adding a “v” : X.XX to your JSON at the root level (where X.XX is the version number). Currently we suggest you use 1.20 (but you can check for the latest version on the website at http://www.blitline.com/docs/api).
The latest version (1.20) provides the following changes in functionality from the default (no “v” specified).
- The content_type of the postback request is set to “application/json” (as it should be).
- Long poll values for “results” are not string encoded (as it should be)
- Image results on errors are a true Hash with “error”, and “failed_image_identifiers” as keys (as it should be).
- Color profile information is preserved automatically
Many people do not use the “v” so for most people this will have no effect, and if it does, it probably just makes Blitline behave the way you would expect it to automatically.
If you wish to ‘opt-out’ of saving color profile information, in your “save” node you can add “save_profiles” : false, and we will strip the color profile information.