Re: touching wsgi file

On Nov 3, 12:31 pm, belred <[EMAIL PROTECTED]> wrote: > thanks for your detailed explanation.  i had to read it 3 times to try > to absorb everything :) i do not need to have the code be portable > beyond mod_wsgi.  if i'm following what you and steve have said and > pages you both pointed me

Re: touching wsgi file

thanks for your detailed explanation. i had to read it 3 times to try to absorb everything :) i do not need to have the code be portable beyond mod_wsgi. if i'm following what you and steve have said and pages you both pointed me to, it appears if i want to share global data i really need to

Re: touching wsgi file

On Nov 3, 9:55 am, belred <[EMAIL PROTECTED]> wrote: > i am using linux and i am using mod_wsgi to run django. > > i don't understand this sentence. > > "This should only be done for daemon processes and not within the > Apache child processes"... > > we have many apache child process.  if i

Re: touching wsgi file

i am using linux and i am using mod_wsgi to run django. i don't understand this sentence. "This should only be done for daemon processes and not within the Apache child processes"... we have many apache child process. if i follow this code: if environ['mod_wsgi.process_group'] != '':

Re: touching wsgi file

On Nov 3, 7:09 am, belred <[EMAIL PROTECTED]> wrote: > is touchingt the wsgi file supposed reload every file in the the > entire django project or just just reload the one wsgi file? If you are talking about the WSGI script file when using Apache/ mod_wsgi, it depends on how you have

touching wsgi file

is touchingt the wsgi file supposed reload every file in the the entire django project or just just reload the one wsgi file? thanks, bryan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To