got_milk_eh yahoo.com wrote:
> Hi, in my cherrypy app I have a number of functions
that do some
> processing and either return some results or call
another function to
> display the results. So far I've been using
internalredirect
> (cherrypy.InternalRedirect("/display",
results) to call the display
> functions, passing the results. However return (return
> display(results)) can also work by calling the display
function and
> again passing the results. The trouble with
internalredirect
> is having
> to pass the html path to access a function versus
return using the
> function name. Which is the suggested/best method to
use? Thanks,
IMO the latter is best. InternalRedirect is a fine technique
for Apache,
where everything must be specified declaratively; when
you've already
got Python, why not just call the display function directly?
To devs: Personally, I would not mind if we dropped
InternalRedirect in
a future release.
Robert Brewer
System Architect
Amor Ministries
fumanchu amor.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-users googlegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribe googlegroups.com
For more options, visit this group at http://
groups.google.com/group/cherrypy-users
-~----------~----~----~----~------~----~------~--~---
|