On Monday 12 April 2010 18:24:08 Ilya Sterin wrote: > Thanks Diez. I finally got it to work, deploying as an egg. I didn't > do anything to setup.py, outside of package files modification. This > type of deployment is fine and seems to work well. I did have some > major issues with mod_wsgi on OS X. Not mod_wsgi issue per say, more > of a python 2.6.5 issue (http://bit.ly/9kRbOn). > > As far as JBoss, maybe, I never used it and no one really uses it any > more (at least anyone in the know :-). Standard war containers is all > you need and the deployment model is pretty much drop a war file here > and you're done. I'm sure the same can be done with mod_wsgi, by > embedding the wsgi script and production.ini in the egg.
Well, you certainly could do it - but then, it's not mod_wsgi, but mod_python_app_server. All fine by me, but the question is if it's worth the effort. WSGI is a very slim spec, on top of that django, TG1 & 2 and all the others are set up differently. Java has one way to rule them all, and this has both advantages - and disadvantages. Diez -- 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.
