On 4/11/06, Max Ischenko <[EMAIL PROTECTED]> wrote: > But what about "simpler"/more common things like request, response and error > classes (HTTPError and NotFound)? I'd say promoting them is OK. After all, we > do promote turbogears.config and turbogears.redirect. So these will become:
The reason turbogears.config and redirect came to be is that they actually build on the functionality of cherrypy.config and redirect. They're not just namespace imports. > turbogears.request > turbogears.response > turbogears.http_error > turbogears.not_found For http_error and not_found, I don't think it's clear if the mechanism will be exactly the same as what we have now. We'll certainly still have request and response objects, but their signatures will likely be different in First Class. And, the preferred method of accessing those variables may not be threadlocal proxies any more. (Some things may be in the wsgi environ...) Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
