Hi, another question from me, today. Can someone maybe explain the "big picture" of what happens, when the client/browser makes a request to the pylons application...?
I mean... first the request goes to the paster-server, right (maybe through Apache/Lighttpd, first) ? Then paster somehow forwards the request as WSGI-thingy to pylons, where Routes decodes the request URL? Then, based on the routes match, a controller is started. Somewhere along the way, the request parameters are put into request.params? Then there is request.environ as well. Ideally, the controller returns a Response-object which goes back up the WSGI-chain, until it arrives at the browser. In between, there is the c-object, which is somehow special, but in what way? (apart from the obvious use as "bridge" to the template/view) Hmm... sorry, this sounds pretty strange and very much newbie-like, but I am confused by this. I can grasp some of those internal aspects, but not how it all plays together. Cheers, Martin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
