Hide Forgot
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. Please See: Common: https://github.com/zanata/zanata-common/commit/5ff3ab467656890855f4215cdfc65f53c609760e https://github.com/zanata/zanata-common/commit/97e2583d9f88cce005575da41acabc521b4a8af0 Api: https://github.com/zanata/zanata-api/commit/121e0ef6ae41aae6ef7b40703010cd8061aa86e8 Client: https://github.com/zanata/zanata-client/commit/453949ac2a0788810b4b3a67397fa9c0ace81621 https://github.com/zanata/zanata-client/commit/12a863bdc97b4b7cd95b58c1ca298203790bb2a5 Server: https://github.com/zanata/zanata/commit/3560de777af96e750fc807d414c5ef9c819bb8eb https://github.com/zanata/zanata/commit/8760a0467ceda821bc4a988c164b6ff73db734d3 https://github.com/zanata/zanata/commit/7a0f77e781f0ca37cf55e95e8cd2dd372dbc7875
Verified in Server 2.1 Client 2.2.0-SNAPSHOT Common 1.8.6-SNAPSHOT
Correction: Client 2.0.2-SNAPSHOT