Does your JSON-RPC server return large amounts of data? If so applying HTTP response compression can greatly reduce network traffic and response time, occasionally by a whole magnitude if your JSON structures contain long repeating keys or values.
Today we released a new version of the JSON-RPC 2.0 Client library for Java that adds support for GZIP and DEFLATE compression. These two algorithms are commonly implemented by web servers such as Apache HTTPD and Apache Tomcat.
To enable HTTP response compression in your Java client app:
URL serverURL = new URL("http://example.com/jsonrpc2/"); JSONRPC2Session mySession = new JSONRPC2Session(serverURL); mySession.getOptions().enableCompression(true);
The JSON-RPC client will then set the
Accept-Encoding request header to signal that it can process compressed responses. Note that many web servers don’t have HTTP compression enabled by default so this setting will simply be ignored by them.
To enable compression in Apache Tomcat you need to configure the HTTP connector by setting
compression to “on”.
The JSON-RPC client will then automatically decompress the HTTP responses before processing the JSON payload.
The new version of the JSON-RPC client library also improves HTTP cookie support. It has dropped the primitive internal cookie store in favour of the standard java.net.CookieManager so now cookie expiration and replacement are also handled.