Integration
This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Hi - Thank you for submitting this idea.
We have reviewed both of your support cases regarding compression.
The requests are almost in conflict with each other –
In the first Support Case (TS011330680) the requirement was to have an easier way, outside of extension, to turn off or customize Compression support (client requesting accept-encoding headers) as determined by the Host, in this case DataPower.
Whereas this Idea (TS015908157) sounds like API backend should determine whether HTTP compression is used for responding to the API Client.
However, API gateway, as an intermediary component, handles the compression decision transparently between the API consumer and API backend. The API backend only determines the compression settings for its own responses, based on its configuration and API consumer, in this case DataPower API gateway. The API gateway, on the other hand, decides whether to compress or not compress the responses based on the capabilities of the API consumer.
Perhaps the possible solution is to allow for a dynamic override of both the Invoke (accept-encoding headers) and then use that meta-data to decide how to respond to the Client. Even so, there are couple of complications:
- if we need to do any processing on the response, we would most likely need to uncompress the payload first.
- if there are multiple invokes you may have a mix of different compression types and/or non-compressed responses that need to be aggregated back together at which point to you compress or not. This would involve implementing conflict resolution mechanisms, such as compression negotiation or fallback compression, to handle compression conflicts.
Unfortunately, due to the architectural complications and conflicts we are unable to progress your idea further at this time. The idea has therefore been moved to the not under consideration state. If you would like to discuss this decision further, please contact <ucubuk3@uk.ibm.com>.