Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339846 - [server] Use ETag in /git/commit
Summary: [server] Use ETag in /git/commit
Status: RESOLVED WONTFIX
Alias: None
Product: Orion
Classification: ECD
Component: Git (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-14 04:22 EDT by Tomasz Zarna CLA
Modified: 2015-05-05 14:46 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Zarna CLA 2011-03-14 04:22:32 EDT 
We could detect the case where a GET /git/commit is called for a history state which hasn't been changed since the last /git/commit request. This could be accomplished by using an ETag and/or If-Modified-Since header to make GET return 304 (Not Modified).
Comment 1 Tomasz Zarna CLA 2012-03-16 05:33:39 EDT 
This could make a huge difference when init'ing a new repo on the Repos page. Currently, after the new repo has been added logs for the other repos are fetched again. Adding the new repo should be a quick operation, waiting for the page to reload takes way too much time.
Comment 2 John Arthorne CLA 2015-05-05 14:46:33 EDT 
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:

https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html