> > Okay, I know, but what is not clear is how tg/cherrypy works, for > > example if a child process handling a request starts my new process P > > via Popen and I don't want tg/cherrypy to wait for it to finish in > > other words the execution of my controller should continue after > > launching process P, then can I be guaranteed that tg/cherrypy will > > not decide to kill it's child that started process P and thereby also > > kill that? This can happen with apache but if you tell me that > > tg/cherrypy is different that would be cool. > > It's python that is different. I'm not sure what apache does - most probably > it makes itself process group leader or something, and kills all > subprocesses - but usually, subprocess is fine. > > If you want to, you can also try to daemonize the subprocess, the ASPN > cookbook has a recipe for that.
Sorry, but I don't see how python is relevant here. What is relevant is the threading model of tg/cherrypy regardless of which language is used to implement it but maybe I'm misunderstanding you. So how does tg/cherrypy really work thread-wise and process-wise? There is one process handling a pool of threads each handling a number of request and then they die? Or threads never die? Or there are several processes each handling its own thread pool? You see, there are a finite number of possibilities and I just would like to know which one is actually at work. :) Cheers, Daniel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
