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).