webmcp
view framework/env/request/forward.lua @ 6:5cba83b3f411
Version 1.0.6
Bugfix: class_prototype:add_reference{...} uses now qualified names in SQL queries to allow JOINs
Fixes in the documentation of slot.put_into and trace.debug
Bugfix: class_prototype:add_reference{...} uses now qualified names in SQL queries to allow JOINs
Fixes in the documentation of slot.put_into and trace.debug
| author | jbe/bsw | 
|---|---|
| date | Fri Jan 22 12:00:00 2010 +0100 (2010-01-22) | 
| parents | 9fdfb27f8e67 | 
| children | 
 line source
     1 --[[--
     2 request.forward{
     3   module = module,  -- module name
     4   view   = view     -- view name
     5 }
     7 This function is called automatically to forward to another view, after an action and all its filters have finished execution, if routing mode "forward" has been chosen. Calling request.forward{...} (or request.redirect{...}) explicitly inside an action will cause routing information from the browser to be ignored. Calling request.forward{...} causes all GET/POST parameters of the action to be preserved for the given view.
     9 --]]--
    11 function request.forward(args)
    12   if request.is_rerouted() then
    13     error("Tried to forward after another forward or redirect.")
    14   end
    15   request._forward = args
    16   trace.forward { module = args.module, view = args.view }
    17 end
