> It may not be directly relevant to the comparison being made here, but > since 'thread' and 'process' are being used almost interchangeably > (with reference to hardware and scalability), I think it's worth > noting that some apps have their own implicit state, on top of > whatever explicit state is in the database. It is state like this that > works in a threaded application but which needs to be completely > refactored in a multi-process application, and no amount of switching > database providers will fix that.
Very true, and if you are storing application state in memory in a TurboGears application you're likely going to have trouble scaling. But, the right answer for web-app development is "don't do that" :) My comments assumed that people are storing all state information in the database, or some other "shared" resource with appropriate locking. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
