On Friday 30 January 2009, Graham Dumpleton said something like: > If you don't use WSGIPythonPath or python-path option to > WSGIDaemonProcess, and instead setup sys.path in the WSGI script file > you can ensure that additional directories are prepended. > > import sys > sys.path.insert(0, '/home/wsbuild/wordstream/server/wordstream/src')
I may just do that. > > Other than that, is there any code I need to look for that would > > change the behavior between the original stack and the pure > > mod_wsgi stack? > > Depends on whether CherryPy mod_python adapter was doing any special > stuff. Thank you much Graham for your module and your pointers in the right direction. It turns out that the mod_python->WSGI adapter we had wrapped around CherryPy was using the cherrypy.tree object directly. The CherryPy seems to suggest using the Application object return by cherrypy.tree.mount, which is what I was doing. So it was working for straight http URLs, but not AMF urls. As soon as I made my "application" object point to cherrypy.tree, all began working wonderfully! Thanks again! j -- Joshua Kugler Part-Time System Admin/Programmer http://www.eeinternet.com PGP Key: http://pgp.mit.edu/ ID 0xDB26D7CE --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to modwsgi@googlegroups.com To unsubscribe from this group, send email to modwsgi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
