Michael Bayer wrote: > the way this idea works is that if some wrapping component knows > it needs a transaction, it opens one. then the controller method > participates in that transaction, regardless of whether or not its > marked as @transactional.
Of course, that makes complete sense. As long at the wrapping component knows about the transaction manager (which, clearly, I think it should). >> I am totally with you here, as this is the other side of the coin >> that I brought up above. Open transactions shouldn't be committed >> until the latest possible point. > > yes. im talking specifcally about the way Pylons passes off from > controller to view...right now you call render_response(), which > typically renders the entire template in a buffer before the > controller method has finished. id favor changing the behavior of > render_response() to creating a "deferred" render object which Pylons > explcitly places outside the scope of the controller call (however, > probably still within the scope of enclosing middleware). Makes sense to me. >> I spent some dark days working on J2EE applications, and while there >> isn't a whole lot that is worth emulating in J2EE, the transaction >> handling is something that I actually liked. > > thats where im getting this from. theres subtleties to it that you > cant emulate casually. Yes, the further down the rabbit hole I go, the more clear this is becoming. That being said, I think I am sold on the concept that we have hashed out here. I need to take some time to look at Zope's transaction manager at some point, and see how hard it would be to extract it from Zope, and get rid of any dependencies, so it can easily be packaged up as its own, simple egg. Has anyone done this before? Is anyone interested in taking this up as a project? -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
