Implement Etags on the server and java client to save on bandwidth (and possibly time) when repeatedly performing the same GET operation.
The server will need to generate Etag headers whenever it responds to one of the affected GET operations. It should also try to honor Etag headers when provided by the client, returning 304 (Not modified) responses when the client provided Etag matches the server calculated one.
The client should keep a local data store (xml) with any server returned Etags and try to populate the Etag header whenever performing one of the affected GET operations. It should also be able to handle 304 responses meaning nothing has changed since the last request was done.
Implemented Etag mechanism in both client and server only on the operation to fetch translations, and per the description above.
The client will now print a log line indicating when there was nothing to fetch because its own Etags matched the server's.
Correction: Client 2.0.2-SNAPSHOT