Gzip compression on SOAP/REST responses
Posted: Tue Jan 07, 2014 8:54 am
Hello,
Would you consider compressing HTTP REST Response with gzip algorythm ?
We developped request throttling and request caching after the introduction of rate limit
and quota limit. The main limiting factor is now the QuotaPerHour that is way too low :
X-IndividualQuotaPerHour-Used: xxx
X-RegisteredPayingQuotaPerWeek-Used: xxx
Gzip compression would hugely reduce the size of REST response :
http://ops.epo.org/3.0/rest-services/fa ... A2/biblio/
JSON no compression : 247'411 bytes
XML no compression : 186'325 bytes
JSON gzip : 8'833 bytes
XML gzip : 7'903 bytes
It looks like you're using JBoss application server that may support natively gzip compression.
On the client side, every serious HTTP/REST framework natively support gzip compression.
That would mean instant benefit for everyone with few lines of code.
Let us know
Regards
Luc
Would you consider compressing HTTP REST Response with gzip algorythm ?
We developped request throttling and request caching after the introduction of rate limit
and quota limit. The main limiting factor is now the QuotaPerHour that is way too low :
X-IndividualQuotaPerHour-Used: xxx
X-RegisteredPayingQuotaPerWeek-Used: xxx
Gzip compression would hugely reduce the size of REST response :
http://ops.epo.org/3.0/rest-services/fa ... A2/biblio/
JSON no compression : 247'411 bytes
XML no compression : 186'325 bytes
JSON gzip : 8'833 bytes
XML gzip : 7'903 bytes
It looks like you're using JBoss application server that may support natively gzip compression.
On the client side, every serious HTTP/REST framework natively support gzip compression.
That would mean instant benefit for everyone with few lines of code.
Let us know
Regards
Luc