Ethan Glasser-Camp

In investigating this, I noticed that the `timestamp` argument to `notify_resource_event` is only present in the `payload`, but that doesn't really make any sense (for all the same reasons as...

OK, never mind that last comment -- I think I confused myself. For a given `(resource_name, parent_id, action)`, the `timestamp` should correspond to the `parent_id`'s `collection_timestamp`, so "must" be the...

Even for requests for a simple resource that isn't in a batch request such as `/buckets/abc/collections/plop`, we seem to enter the kinto-fxa code about five or six times in a...

https://groups.google.com/forum/#!topic/pylons-discuss/-1Z5N-hhAOw has some information on the subject.

I could be wrong, but I wonder if 2-phase commit would even be helpful here -- the problem isn't that some transactions succeed and some don't, the problem is that...

A `PUT` can be a create or an update. There's no such thing as `INSERT ... WHERE last_modified = 'previous_last_modified'`.

I think that might be the right approach. Be sure to handle the case of `If-Match`, which has to fail if there is no record with which to conflict.

I would be curious to see your scripts.

No strong feelings. How does this work with synchronization?

Ah, right. I misread this and thought it was about renaming records. Renaming buckets and collections seems OK to me.