On Sun, Nov 16, 2008 at 3:18 PM, Graham Dumpleton <[EMAIL PROTECTED]> wrote: >> . return self.app_iter >> > > Why are you doing it in webob Response class? Do it in the WSGI script > file like LogingMiddleware example in: > > http://code.google.com/p/modwsgi/wiki/DebuggingTechniques > > Because you are inserting this in the middle of the WSGI stack and not > at top in WSGI script file, things in an outer scope could be changing > or adding response objects. > > Graham >
Thank you very much, Graham. Once I got the right diagnostic tool plugged in the right place, the errors (some of them, at least) were quickly found. That LoggingMiddleware did the trick. And reading through the debugging page on the modwsgi website answered most of my questions on how the start_response function fit in. I was thinking there was one start_response function, necessarily at the top; In reality, there can be a start_response at each level of the stack, each calling the start_response at the next lower level. Thank you for the work you've put into modwsgi, and into documenting it, and also for your tact in telling me to "rtfm". David -- [EMAIL PROTECTED] Pitcher's Duel -> pitchersduel.python-hosting.com .. and thank you to the rest of you for watching me flounder around in this thread without negative comment. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
