Use content version as etag
Reported by Ben Hood | 2011-09-06 11:50:18 UTC
When requesting content by id from participants, the content version should be used as an etag. This will ensure:
- That the agent knows what actual version of the data it has received when it requests content
- The participant could return a 304 for data that has not changed
Comments and changes to this ticket
-
Paul Jones 2011-09-06 11:52:01 UTC
We could probably also proxy the HTTP conditional request headers - eg, If-None-Match - to allow for end-to-end conditional requests.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Ben Hood