Re: So why are things being executed twice on every transaction?
Naveen Chawla <[email protected]>
| Newsgroups | gmane.comp.java.prevayler |
|---|---|
| Message-ID | <CAGs7EcWcpYgMYc=1qco-ZVWE_fkRSbVDPPKAEgyedpo+spn5FA@mail.gmail.com> |
You are right in everything you say, except that's "configureTransactionDeepCopy". I was talking about "guaranteeTransactionDeepCopy", which is used only by the StrictTransactionCensor. Deep copies are still guaranteed when the user does nothing (as it's default) even if "guaranteeTransactionDeepCopy" is removed completely. It is only a variable used during direct-mode to prevent "direct transactions" happening twice. On 8 November 2011 14:47, Justin T. Sampson <[email protected]> wrote: > On Tue, Nov 8, 2011 at 12:45 AM, Naveen Chawla <[email protected]> > wrote: >> >> Remove "guaranteeTransactionDeepCopy" (new) and all uses of it (both >> method and variables, since it's only used to force deep-copy during >> food-tasting to prevent direct-mode from acting twice on the same >> references). > > That doesn't sound right. The food taster should have always been > deserializing. If the user calls guaranteeTransactionDeepCopy that should > force deserializing against the "real" prevalent system as well. So the > option is relevant even without the food taster in the picture. > ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion _______________________________________________ "Databases in Memoriam" -- http://www.prevayler.org