> Hmm, not really I believe... Take close look at the code I posted. The > default() method needs to see what arguments were passed as positional > args to calculate how many elements it needs to pop from PATH_INFO into > SCRIPT_NAME. Unless TG stores this info somewhere in the request object > there's no way to get it from inside use_wsgi_app
Yes, we would have to put the info back into the request as we dispatch. So, the real question is what API do we want to expose for this, and I'm torn. >> One use case of use_wsgi_app was that's not covered by the above >> example is that we wanted it to be simple to just return the response >> OR for the controller to monkey with the response on the way out. > Hmm, subclass and override "default"? Anyway, I've made it more explicit > b adding a "delegate" method and documenting in its docstring thta you > can use it for that purpose Yea, that works. And in the most cases people aren't modifying the response body on the way out. --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
