As Diez pointed out on my post about tgext.mobilemiddleware using use_custom_format to switch template inside a controller method causes a few concurrency problems. Also I saw that the template switch is persistent (each and every request after the one that switched the template gets the new template).
I have been able to solve the tgext.mobilemiddleware problem by simply relying on what override_template does, but use_custom_format is referred multiple times inside the documentation as a way to change the rendered template between the registered custom ones during a request. I think that it should be more correct to have the template switch saved inside the request itself instead of saving it inside the decorated controller object, this would solve both the concurrency problems and the template switch persistance. Is there any reason not to change the current behaviour? Alessandro -- 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.
