On 8/22/08, dbrattli <[EMAIL PROTECTED]> wrote: > > Hi, > > With TG-1.5 we can now run database transactions as a CP3 tool instead > of @expose. That way you can easily decide which controllers that gets > transactions and who don't by only enabling/disabling the CP3 tool for > specific controllers. I think it would be nice to get transaction > handling away from expose/entangle. So I've written a CP3 tool to > handle transactions.
The idea seems interesting. We should think about the implications. Factoring the transactions handling out of the tg core is one of the improvements of tg2. But to get this refactoring moving we would need to have an easy to install tg1transaction manager. I am wondering if we could not use remoze.tm in tg 1.5 since CP3 is wsgi compliant... This would make us even more close to tg2. I'll need to think about this after tonight releases :) Florent. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
