[gme-users] Nested transactions
peter.volgyesi at vanderbilt.edu
Thu Aug 5 09:27:06 CDT 2010
I wonder what do you gain by having a "root transaction". In your
interpreter you can have fine grained transaction logic (I guess we
call this "custom transactions" in the interpreter wizard and/or in
the componentconfig.h file). So, your interpreter can commit changes
any time to trigger the add-ons (and GUI), but why do you need an all
encompassing transaction in this case ?
On Thu, Aug 5, 2010 at 7:52 AM, James H. Hill <hillj at cs.iupui.edu> wrote:
> Hi Peter,
> Ah, I see. Thanks for the quick reply.
> Are there any plans to make sure a feature available in interpreters? I can
> see a case were you may have an interpreter that:
> . starts a root transactions
> . makes incremental updates to the model in nested transactions
> . commits its current modifications to force the *add-on* to execute
> . commits root transactions once everything is complete
> I would think that nested transactions would make this use cause much easier
> to implement without *duplicating* a LOT of code. Or, do you know a
> workaround for *emulating* nested transactions in interpreters to prevent
> duplicating a LOT of code or causing tight coupling of code?!
> On 8/5/10 8:42 AM, Peter Volgyesi wrote:
>> Nested transactions are used only inside MGA (to implement add-on
>> notifications in which add-on can further modify the models).
>> On Wed, Aug 4, 2010 at 5:23 PM, James H. Hill<hillj at cs.iupui.edu> wrote:
>>> Does anyone know if GME supports nested transactions in it's
>>> interpreters, and how to do so?!
>>> I see that there is an enumeration value TRANSACTION_NON_NESTED, but
>>> there is no TRANSACTION_NESTED value. I only see TRANSACTION_GENERAL,
>>> which seems to not support nested transactions.
>>> Any help would be greatly appreciated.
>>> gme-users mailing list
>>> gme-users at list.isis.vanderbilt.edu
More information about the gme-users