On March 2, 2010, James Westby wrote: > There would be a couple of ways of fixing this, such as exporting > bug_heat as a method not as an attribute. >
I think we should have a way to mark attribute that shouldn't be part of the etag computation. > We already have something like this with, at least, code, where you race > with the scanner when pushing up a branch and then modifying an > attribute of the branch over the API. > > You could argue that script authors should deal with 412 errors, as they > can happen with concurrent user edits and the like. While that is true, > I'm not sure we need to be making it more likely to happen, and racing > with automated tasks is less or a reason to conflict anyway. Plus, the > facilities for handling conflicts in the API are lacking from where they > should be if all API users should be dealing with them. -- Francis J. Lacoste [email protected]
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
