Re: JournalDiskSyncStrategy?

Karl Wettin wrote:

> Thanks for the suggestions, but I'm afraid they're not applicable
> for my case due to the transactions being interdependent on each
> other, e.g. I might not have enough information to produce my
> second transaction unless the first already has been executed.
> This syncronized singleton delta evaluator of mine is all about
> fixing isolation.

Okay, one last thought -- if you've got 199 things that you don't
want to trigger a sync followed by 1 thing that you do want to
trigger a sync, might it be possible that those initial 199 things
should be queries rather than transactions? That is, can you use a
series of queries to determine the deltas, without modifying the
prevalent system, followed by a single transaction applying all the
deltas at once?

(I don't mean to stand in the way of your proposed change, but it's
an interesting design question to explore!)

Cheers,
Justin

------------------------------------------------------------------------------
_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org