All, I just committed a quick change to TurboGears 2.0 that has an effect on the way you all probably expect your applications to work, but is an important bug fix: http://trac.turbogears.org/changeset/4025.
The summary is this: Pylons expects all requests to occur in fresh controller instances, and `TurboGearsApplication` was keeping around a cached version of the root controller, and re-using it in order to not have to re-construct the entire object tree on every request. However, since Pylons expects fresh instances, this was causing response data to "leak" into subsequent responses. For the time being, I have updated TG2 to always return a freshly constructed instance of the root controller and use that to process requests. This introduces some overhead, but actually produces correctness, which is much more important at this stage in the game :) At some point, we should start considering how we can optimize this a bit, to prevent having to re-construct the entire tree on every request. -- Jonathan LaCour http://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
