On 18 Oct 2017, at 19:46, Evgeny Khramtsov <[email protected]> wrote: > > Wed, 18 Oct 2017 16:43:54 +0100 > Kevin Smith <[email protected]> wrote: > >> It’s much easier to keep a global lookup table if you don’t have to >> deal with conflicts because the identifiers are node-specific - >> that’s where the gain in not needing the (effective) lock comes in >> here. > > You still need to resolve conflicts for any global table if you want to > be partition tolerant.
You do, but if the responsible node is encoded into the resource, it’s always a case of binning the old one and using the new one. Or, at least, there are clustering strategies where this is true, and if using them it buys you a lot to be able to do this “bin it and trust the new value” resolution. This applies to the other data associated with the session too. /K _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
