In both cases that can be implemented as a form of "rendering". The body can be tought of as being 'rendered-into', say, body.text (which would hold a simple string object) or something, that happens at the end of the current request-processing cycle. Similarly, user-name/info could be rendered by the auth mechanism into some buffer, and the session-mechanism would store that buffer in, say, session.user.
This way I could do 'request.body.text' and 'response.body.text' regardless of the underlying http-machinery, and 'session.user.first_name' and 'session.user.last_name' regardless of the session-storing mechanism and authorisation-implementation. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
