Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      story #7704 manage concurrent artifact edition in REST
    Actions
    Summary
    Empty
    manage concurrent artifact edition in REST
    Empty
    may need to implement etags on
    - PUT artifacts/:id
    - GET artifacts/:id
    - GET trackers/:id/artifacts
    - GET tracker_reports/:id/artifacts

    - sending invalid Etag => 409 conflict
    - should not break calls with no etag header

    Note: concurrent edition might already be managed informally (E.g. last modified headers)- check before going any further.
    Empty
    Empty
    Status
    Empty
    Done
    Development
    • [ ] Does it involves User Interface? 
    • [ ] Are there any mockups?
    • [ ] Are permissions checked?
    • [ ] Does it need Javascript development?
    • [ ] Does it need a forge upgrade bucket?
    • [ ] Does it need to execute things in system events?
    • [ ] Does it impact project creation (templates)?
    • [ ] Is it exploratory?
    Empty
    Details
    #7704
    dylan bowden (dylan)
    2015-03-25 18:36
    2014-12-17 16:00
    7705

    References
    Artifact links
    Empty
    Referencing story #7704

    Artifact Tracker v5

    rel #7907 8.0
    request #9230 Artifact API doesn't follow RFC

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/96/3696/1' of ssh://gerrit.tuleap.net:29418/tuleap into stable 0ba46f85f6
    User avatar Nicolas Terray (nterray) , 2015-03-06 09:47
    story #7704: manage concurrent artifact edition via REST ecd3d66610
    User avatar dylan bowden (dylan) , 2015-03-05 15:32
    Merge commit 'refs/changes/04/3704/2' of ssh://gerrit.tuleap.net:29418/tuleap into stable e4a60f6830
    User avatar Nicolas Terray (nterray) , 2015-03-09 14:30
    story #7704: manage concurrent artifact edition via REST 4bf2650636
    User avatar dylan bowden (dylan) , 2015-03-09 11:08
    Referenced by story #7704

    Other

    gerrit #3696
    Display settings

    Follow-ups

    User avatar
    dylan bowden (dylan)2015-03-05 10:41
    last edited by: dylan bowden (dylan) 2015-03-05 10:41

    Found a very interesting article on the subject http://blog.4psa.com/rest-best-practices-managing-concurrent-updates.

    Unless there are objections, I'm not going to implement Etags for the moment. I'll add the Last-Modified and If-Umodified-Since headers as I think they are enough to cover the use cases. The reason for this is that Etags may be useful at a later date when we want to start optimising cached requested and I don't want to implement something now that might not be a nuisance later.