Bug 888090 - [RFE] Implement REST ETag mechanism for certain GET operations.
Summary: [RFE] Implement REST ETag mechanism for certain GET operations.
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-Logic, Component-Maven, Performance
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 2.1
Assignee: Carlos Munoz
QA Contact: Alex Eng
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-18 00:33 UTC by Carlos Munoz
Modified: 2013-02-26 04:06 UTC (History)
3 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2013-02-26 04:06:26 UTC


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.