43
edits
Lightning implementing RFC6638: Difference between revisions
Jump to navigation
Jump to search
→Schedule Tag Implementation
Mohitkanwal (talk | contribs) |
Mohitkanwal (talk | contribs) |
||
| Line 155: | Line 155: | ||
| <s>A response to any successful COPY or MOVE request that specifies a Destination request header targeting a scheduling object resource MUST include a Schedule-Tag response header with the value set to the same value as the CALDAV:schedule-tag WebDAV property of the destination resource. </s>|| Lightning does not need to implement || Example | | <s>A response to any successful COPY or MOVE request that specifies a Destination request header targeting a scheduling object resource MUST include a Schedule-Tag response header with the value set to the same value as the CALDAV:schedule-tag WebDAV property of the destination resource. </s>|| Lightning does not need to implement || Example | ||
|- | |- | ||
| Clients SHOULD use the If-Schedule-Tag-Match header on requests that update scheduling object resources, instead of HTTP ETag-based precondition tests (e.g., If-Match). Normal ETag-based precondition tests are used in all other cases, e.g., for synchronization.|| | | Clients SHOULD use the If-Schedule-Tag-Match header on requests that update scheduling object resources, instead of HTTP ETag-based precondition tests (e.g., If-Match). Normal ETag-based precondition tests are used in all other cases, e.g., for synchronization.|| Should it send it all the time?[http://tools.ietf.org/html/rfc6638#appendix-B.3]|| Same as the first case. If present in mItemInfoCache then send the If-Schedule-Tag-Match header. | ||
|- | |- | ||
| Clients MAY use the '''If-Schedule-Tag-Match''' request header to do a PUT request that ensures that "inconsequential" changes on the server do | | Clients MAY use the '''If-Schedule-Tag-Match''' request header to do a PUT request that ensures that "inconsequential" changes on the server do not result in a precondition error. || Client must Handle Error Case where schedule-tag does not match|| Example | ||
|- | |- | ||
| Clients MAY use the If-Schedule-Tag-Match request header to do a '''DELETE''', <s>COPY</s>, or <s>MOVE</s> request that ensures that "inconsequential" changes on the server do not result in a precondition error. || Client must Handle Error Case where schedule-tag does not match|| Example | | Clients MAY use the If-Schedule-Tag-Match request header to do a '''DELETE''', <s>COPY</s>, or <s>MOVE</s> request that ensures that "inconsequential" changes on the server do not result in a precondition error. || Client must Handle Error Case where schedule-tag does not match|| Example | ||