Without the global transaction counter another problem arises. Suppose transaction B depends on ( results of ) transaction A. And they are executed from different threads. However they have the right order when executing the first time.
How to guarantee that the execution order is the same when transactions are replayed? On Fri, Dec 4, 2009 at 6:40 AM, John Harrop <jharrop...@gmail.com> wrote: > On Thu, Dec 3, 2009 at 6:31 PM, Sergey Didenko > <sergey.dide...@gmail.com>wrote: > >> >> In comparison with Prevayler, the persister does not block the reads, >> because it relies on Clojure STM. However it blocks the writes as >> Prevayler, because currently there is no way to reliably get/ generate a >> transaction id without locking. >> > > What about thread-local allocation blocks of IDs? This reduces the locking > to when one of those blocks is exhausted. > > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
