> By forking you for the entire > web-server (or proxy) with lots of memory overhead and lots on > potential consequences.
I've solved a similar problem by having web2py make a system call to a separate python script that demonizes itself immediately (http://code.activestate.com/recipes/278731/). The web-server then returns and is free to go about it's business. My daemon script can then fork (or in my case I use the multiprocessing module) till it's hearts content. The last hurdle is to have the web-server talk to the daemon. I do it through simple log files but you could get fancier with sockets and/or pickles. I make ajax calls every 0.5 seconds to update the HTML content. Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
