On Dec 19, 2006, at 11:39 AM, Mike Orr wrote: > The "Pylons Execution Analysis" I posted last week > (http://sluggo.scrapping.cc/python/) may help to get a handle on those > files and how the framework uses them. It's a bit too detailed for > beginners but I wanted to get everything down for reference, and maybe > some of it can be packaged in a more user-friendly form later.
Forgot to reply to the other thread where you announced the tutorials Mike, but that execution analysis is great, I even saw a few things I hadn't known about before (mainly the lower level socket threads). :) I think it also provides a pretty good overview for what JJ was talking about, with how Pylons takes a cross of the "everything-in- the-framework" to the "everything in your app" approach. I've considered doing what Ian mentioned as well and having more of the stack built in the framework, but that'd make it a bit more work to drop in your own middleware then since you'd have to recreate that section should you want to add something. Thus the decision to keep the middleware assembly in there, I think it also helps when you can see your applications WSGI stack being built in your app, instead of having the framework sweep it under the rug and just do it all "automagically". Cheers, Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
