Dear Graham, 

a big Thank You for mod_wsgi! 

I just tried for the first time two django instances on different ports - 
and had the problem that 
the instances (which have several common UURLs like /study/, /research/ ) 
seemed to be
mixed up. 

So I tried and googled and used daemon mode and changed 
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "X.settings") to 
os.environ["DJANGO_SETTINGS_MODULE"] = "X.settings" - with no success. 

Then I tried your debugging code from 
http://code.google.com/p/modwsgi/wiki/DebuggingTechniques 
and learned a lot. -

 BTW, there is a small slip in  the second (long) code block 
of the subchapter "Tracking Request and response": the line 

pprint.pprint((status, headers)+args), stream=self.__oheaders)
must be
pprint.pprint((status, headers)+args, stream=self.__oheaders)

But all this didn't solve my problem... which was totally unrelated to modwsgi: 
If both django instances use the same memcached daemon for caching, 
*one must set  *CACHE_MIDDLEWARE_KEY_PREFIX  to different values for each 
instance!

Seemingly, the cache mechanism uses only local parts of the URLs and not 
port numbers etc.

So I feel stupid and perhaps this mail helps somebody else.

- Maik
 

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to modwsgi+unsubscr...@googlegroups.com.
To post to this group, send email to modwsgi@googlegroups.com.
Visit this group at http://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to