Hi, I haven't done a fastcgi deployment myself, but the typical model with fastcgi is a forked process mdoel. Each process uses only one thread. So, storing shared data on your root controller is not beneficial.
Kevin On 3/9/06, pc <[EMAIL PROTECTED]> wrote: > > Hello all, > I try to figure the execution model of fastcgi. I am using the > tg_fastcgi script which is on trac. > > Whenever there are a few tg_fastcgi processes running, does it mean > that each one of them > have its own instance of my root controller? > > If so, then it is pointless to have state variables (like list of > logged in users) inside the root controller, right? and all state data > should be in files/database - including sessions. > > Does each fastcgi process in itself use threads to serve several > requests concurrently? > > Thanks, > pc > > > > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
