Etag handling in Attract shots #49555

Open
opened 2016-10-04 10:44:41 +02:00 by Sybren A. Stüvel · 2 comments

We should consistently handle Etags in Attract. At the moment we have the following shot operations. Create operations are not listed, since there is no Etag handling needed then.

  • PATCH from Blender
  • PATCH from Web
  • Delete from Blender

The question mostly is whether we'll do Etag checking at all for these operations.

Tasks are less interesting, since we can only edit them from the web, and with simple PUT requests. This means that we can keep the current Etag handling (PUT only allowed if your web form contains the current Etag).

We should consistently handle Etags in Attract. At the moment we have the following shot operations. Create operations are not listed, since there is no Etag handling needed then. - PATCH from Blender - PATCH from Web - Delete from Blender The question mostly is whether we'll do Etag checking at all for these operations. Tasks are less interesting, since we can only edit them from the web, and with simple PUT requests. This means that we can keep the current Etag handling (PUT only allowed if your web form contains the current Etag).

Changed status to: 'Open'

Changed status to: 'Open'

Added subscribers: @dr.sybren, @fsiddi

Added subscribers: @dr.sybren, @fsiddi
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: archive/pillar#49555
No description provided.