Jonathan LaCour schrieb: > 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 :)
One suggestions to those working on the trunk: Please add comments to the code explaining why you do such non-obvious things, so that other developers some months later don't start to cache controllers again, believing this is a good idea that nobody had so far. In the 1.0 branch, things were often changed back and forth because the original developers moved on to other projects and nobody else really understood the background why e.g. a certain call was made, and whether it was necessary or not. A simple comment by the original author could have clarified this and would have spared us much trouble. -- Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
