The title pretty much say what I need 1) Retrieve the page - page must not be changed starts NOW 2) Do something what requires user input, possibly may last few minutes 3) Save the page ONLY if it wasn't changed, if it was, go back to step 1 this all needs to be done using API, I thought that edit token would help me here, so that I would fetch the token at step 1 and edit using it at step 3, hoping it expire if someone edit the page meanwhile. But this doesn't seem to work according to documentation, because edit token is only changed when user logout. Is there any super-safe and proper method to do this? Preferably something more reliable than just storing the timestamp and comparing it (in theory someone could edit the page even in short time when timestamp is compared). I need some super-safe lock that prevent all possible race conditions here. _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

In documentation I see: basetimestamp: Timestamp of the base revision (obtained through prop=revisions&rvprop=timestamp). Used to detect edit conflicts; leave unset to ignore conflicts starttimestamp: Timestamp when you obtained the edit token. Used to detect edit conflicts; leave unset to ignore conflicts What is difference between these two? Documentation say that there is only 1 edit token which is changed only when user log out / log back. However that makes no sense when description of starttimestamp tell something about "Timestamp of token". Is there really only 1 edit token? Is it really same for all pages? Does it really change only when user relog? How does it change for IP users? On Wed, Jan 22, 2014 at 12:47 PM, Brian Wolff <bawolff(a)gmail.com> wrote: > On Jan 22, 2014 7:41 AM, "Petr Bena" <benapetr(a)gmail.com> wrote: >> >> The title pretty much say what I need >> >> 1) Retrieve the page - page must not be changed starts NOW >> 2) Do something what requires user input, possibly may last few minutes >> 3) Save the page ONLY if it wasn't changed, if it was, go back to step

_______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

On Wed, Jan 22, 2014 at 4:11 AM, Brian Wolff <bawolff(a)gmail.com> wrote: basetimestamp corresponds to wpEdittime in the web UI. If this doesn't match the top revision's timestamp, it is an edit conflict (which might be automatically resolved, just as with the web UI). Omitting it prevents any detection of such edit conflicts, meaning you're likely to just overwrite someone else's edit. starttimestamp corresponds to wpStarttime in the web UI. It is used to detect situations such as "article was deleted since I started editing it". Omitting it means that you might recreate an article that has been deleted, or restore the deleted version if the article was deleted and then partially restored. -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

On 01/22/2014 12:35 PM, Petr Bena wrote: basetimestamp (the timestamp of the revision your edit is based on) should be sufficient. I might be missing something, but I can't think of a scenario where: 1. Get the ID and timestamp of the last revision. 2. Get the text of that revision. 3. Do long-running computation based on that text. 4. POST an edit (resulting from that computation) with basetimestamp set to the timestamp obtained in #1. will cause a race condition.

Matthew Flaschen _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

http://restpatterns.org/HTTP_Headers/If-Unmodified-Since It should be passed a value that matches a Last-Modified value that we get from the previous "fetch page contents" API call.