2008/12/31 julio33 <[email protected]>: > > I think mod_wsgi is the right way for my application, in a first > moment i would use > the paste webserver, but i don´t sure about that, i thought that > apache is strong, > secure and whatever, my application is actually very simple, you only > query a > string, it search on a database and answer a string, that´s all, but i > still prefer > apache, i don´t know if that´s the right election. > > The strings all are of them very short.
In practice, most Python web applications that people run will work okay no matter which hosting mechanism is run. One wouldn't necessarily expect to see too much difference in the way of performance either, so long as hosting mechanism is not configured in a stupid way, as the bottleneck is typically going to be in the web application or any database access. This overhead tends to dwarf any benefits that one might get from web server layer from using one hosting mechanism over another. Thus more important to use a hosting mechanism that you personally find easy to deal with and fits your mindset of how it works. This is what I find some of the Pylons folks just don't accept, that is, that other options are going to be just as good for most use cases so doesn't really matter what one selects. As I said, to them there is only one solution as far as they are concerned. I accept that there are various solutions and no perfect one. Graham > Julio > > On 30 dic, 19:41, "Graham Dumpleton" <[email protected]> > wrote: >> 2008/12/31 julio33 <[email protected]>: >> >> >> >> > Well actually was named "wsgi" not "mod_wsgi"...just a confussion >> > typing here, but there was people >> > there... >> >> Okay, know the one. Frequented by Pylons people who think that Paste >> HTTP server and mod_proxy are only true way to do things and that >> mod_wsgi is evil. ;-) >> >> Graham >> >> > Julio >> >> > On 30 dic, 19:31, "Graham Dumpleton" <[email protected]> >> > wrote: >> >> 2008/12/31 julio33 <[email protected]>: >> >> >> > Really thanks, >> >> >> > The irc channels were the mod_wsgi but there nobody answer me >> >> > anything, >> >> >> Hmmm, where is there a mod_wsgi channel? I don't recollect any such >> >> thing on traditional IRC such as at at freenode. Sure you didn't >> >> create your own empty channel. >> >> >> Graham >> >> >> > maybe they were eating or something, and the others were a >> >> > python generic channel and the slicehost channel all of them on >> >> > freenode, well in the slicehost somebody help me a little. >> >> >> > Actually i never want to reload the script, i wanted the script was >> >> > always on because i thought that´s the more efficient way(maybe i´m >> >> > wrong) >> >> >> > However now i know what i want, thanks i will be watching the list. >> >> >> > Thanks, >> >> > Julio >> >> >> > On 30 dic, 19:03, "Graham Dumpleton" <[email protected]> >> >> > wrote: >> >> >> 2008/12/31 julio33 <[email protected]>: >> >> >> >> > Wow you are really fast answering :) >> >> >> >> > I was talking about this: >> >> >> >> >http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide >> >> >> >> That document is intended to be simplistic on the issue of reloading, >> >> >> otherwise confuses people. :-) >> >> >> >> > You rocks, i have been asking this on 3 irc channels and nobody >> >> >> > answer >> >> >> > anything logical :) >> >> >> >> Which irc channels? I monitor some relevant ones, but not others >> >> >> because some people on the latter don't really appreciate mod_wsgi and >> >> >> talk a lot of crap/misinformation about it. Had to give up trying to >> >> >> correct them as too much of a waste of time. >> >> >> >> > I read the document and it seems that it only reload it when there >> >> >> > are >> >> >> > changes. >> >> >> >> > So if i don´t make any changes in my file, my app will be everytime >> >> >> > up >> >> >> > in memory and >> >> >> > will not be called everytime, or i´m wrong? >> >> >> >> More or less. The important thing is that in embedded mode, a shallow >> >> >> reload only is done, ie., just the WSGI script file. In daemon mode, a >> >> >> deep reload is done, ie., whole process restarted. Thus in daemon >> >> >> mode, if changing code in imported Python modules, just touch the WSGI >> >> >> script file and it is enough to restart the WSGI application without >> >> >> restarting whole of Apache. >> >> >> >> Important therefore to know for sure you are using embedded mode or >> >> >> daemon mode. >> >> >> >> For a bit more of different process/threading models read: >> >> >> >> http://code.google.com/p/modwsgi/wiki/ProcessesAndThreading >> >> >> >> Graham >> >> >> >> > Thanks >> >> >> >> > On 30 dic, 18:45, "Graham Dumpleton" <[email protected]> >> >> >> > wrote: >> >> >> >> 2008/12/31 julio33 <[email protected]>: >> >> >> >> >> > hello, i was using cgi with python and decided to went to >> >> >> >> > mod_wsgi, it >> >> >> >> > works great, but i have a doubt...when i was reading the tutorial >> >> >> >> > it >> >> >> >> > says that everytime i made a change in my script file i MUST >> >> >> >> > restart >> >> >> >> > apache2 to watch the changes, >> >> >> >> >> Which tutorial? >> >> >> >> >> > this is ok to me, but i don´t understand >> >> >> >> > why when i tried by error to change the script and use it WITHOUT >> >> >> >> > restarting apache it works according to the new changes, i thought >> >> >> >> > this is not right, because it´s supposedly to charge application >> >> >> >> > everytime apache starts, so if when i made changes the things >> >> >> >> > change it >> >> >> >> > ´s like it´s calling again and again the file, just like cgi >> >> >> >> >> Start by reading: >> >> >> >> >> http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode >> >> >> >> >> Graham > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
