One thing I seriously debated was whether a single Pylons instance would be used per app, or, whether a single Pylons instance would have multiple controllers, each handling a separate Facebook application.
Currently, I have one Nginx with uWsgi (4 threads on a quadcore) that talks to a single Pylons instance. I have three different Facebook applications that utilize the Pylons virtualenv and three separate controllers. While the applications are somewhat interconnected and share the same database, tables are separated with prefixes for the non-interconnected pieces. I do have two other apps, one that uses Apache2/mod_wsgi/Django and one that uses Apache2/mod_wsgi/Pylons. I'm working on another using Nginx/uwsgi and Tornado for a portion. In my case, I felt creating separate virtualenvs outweighed some of the other issues I would run into. Whether my requirements justify a more generic approach, I don't know. As for whether it should be middleware, or a new controller, I think I would like to avoid it being middleware, though, I can see advantages for both. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
