On Jan 18, 3:26 am, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > In newer TurboGears versions, the multi process problem goes away if > using SQLAlchemy instead of SQLObject as it doesn't have the caching > issue. Thus, when SQLAlchemy is used, you can do the mod_proxy load > balancing thing. Alternatively, you can use mod_wsgi and thereby get > parity with Django in the sense of being able to deploy it in same > Apache configuration.
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. -- Ben Sizer --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
