On Fri, Mar 1, 2013 at 4:47 AM, Michael Dürig <mdue...@apache.org> wrote: > ...What Jukka is saying is that the repository gives you a choice between > consistency and availability. Since both you cannot have....
+1 to having that, as long as those choices are made clear to users. Log messages that explain what's happening (*) would be good to have, in all cases where settings affect CAP behavior. -Bertrand (*) for example "CAP:the FOO option is currently set for availability. at the expense of consistency"
