As XMLA responses are verbose and can become very large, I think it is important that OLAP4J supports HTTP gzip encoding. Activating gzip encoding on servers like Tomcat takes 1mn, and implementing support for it in Olap4J is also a simple task:
Olap4J would have to expose the following HTTP header line to tell it supports GZip encoding:
Then the server will send compressed HTTP payloads, that can be uncompressed with a GZipInputStream.
Log in to post a comment.