Bug 888090

Summary: [RFE] Implement REST ETag mechanism for certain GET operations.
Product: [Retired] Zanata Reporter: Carlos Munoz <camunoz>
Component: Component-Logic, Component-Maven, PerformanceAssignee: Carlos Munoz <camunoz>
Status: CLOSED CURRENTRELEASE QA Contact: Alex Eng <aeng>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.0CC: aeng, sflaniga, zanata-bugs
Target Milestone: ---   
Target Release: 2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 2.1.x Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-26 04:06:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Carlos Munoz 2012-12-18 00:33:22 UTC
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.

Comment 3 Alex Eng 2013-01-02 02:36:48 UTC
Verified in 
Server 2.1
Client 2.2.0-SNAPSHOT
Common 1.8.6-SNAPSHOT

Comment 4 Alex Eng 2013-01-02 02:37:20 UTC
Correction: Client 2.0.2-SNAPSHOT