On Thu, May 12, 2016 at 10:32 AM, Jen Smith <jendaboar...@yahoo.com> wrote: > > My question is if this can be addressed via software by (using? abusing?) > the client provided timestamp field and forcing it to be continuously > increasing, and what unexpected issues may arise from doing so?
I'm not sure if you're looking for an answer for your own particular use-case(s), or something more general, but I thought I'd point out that client-provided timestamps are as much a feature in other contexts as they are a bug in this one, precisely because they *can* be out of order; They are meant to represent a causal ordering. In other words, if you somehow unconditionally enforced monotonicity on the server side[*] you'd break a whole other set of use-cases. [*]: But, how would you even manage such a thing without coordination, in a distributed environment? -- Eric Evans john.eric.ev...@gmail.com
