redirect vs return

pytrade wrote:
> I've been using the following for redirects:
> 
> raise cherrypy.HTTPRedirect(url)
> 
> It however seems rather inefficient (if my
understanding is correct).
> Is there a way to forward to a different url without
having to do
> another round turn with the browser.

You mean something other than:

    return cherrypy.root.different.url.handler(args, kwargs)

?


Robert Brewer
System Architect
Amor Ministries
fumanchuamor.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-usersgooglegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/cherrypy-users
-~----------~----~----~----~------~----~------~--~---

No I would want something like:

raise cherrypy.HTTPRedirectInternal(url)

Where the exception would discard all my custom decorators
and restart
a new request without having to leave the current server
process.

One question I have is that does using the current <raise
cherrypy.HTTPRedirect(url)> return the request to the
browser
requesting the client to load a new url or is it smart
enought to
internally redirect to the new url.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-usersgooglegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/cherrypy-users
-~----------~----~----~----~------~----~------~--~---