Closed
Bug 706811
Opened 13 years ago
Closed 12 years ago
Implement 304 on the collection GET
Categories
(Web Apps Graveyard :: AppsInTheCloud, defect, P4)
Web Apps Graveyard
AppsInTheCloud
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: tarek, Assigned: tarek)
Details
(Whiteboard: server)
- GET provides an ETag value - the client may provide an If-None-Match header if the collection was not changed since then, the GET returns a 304 Not Modified The clients can use this to poll against the GET, and avoid hitting the Database when no changes where made
Comment 1•13 years ago
|
||
Note that XHR requests do not always work well with this technique, as the browser's own cache can get in the way.
OS: Linux → All
Hardware: x86 → All
Assignee | ||
Updated•13 years ago
|
Priority: P2 → P4
Updated•13 years ago
|
Whiteboard: server
Comment 2•12 years ago
|
||
A Pivotal Tracker story has been created for this Bug: https://www.pivotaltracker.com/story/show/24808923
Comment 3•12 years ago
|
||
The old app sync codebase is no longer going to be supported. Apps in the cloud will be under a different codebase. None of these bugs are valid anymore.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Updated•6 years ago
|
Product: Web Apps → Web Apps Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•