> Presumably you are also using WSGIApplicationGroup to also force use > of same sub interpreter in process, else they will still all be > distinct, just in same process. Yes, we are using LXML so we need to use %GLOBAL% as WSGIApplicationGroup.
> Which is all fine if you manage your code. We are using some external libraries, like LXML, and others. Thus if any of these contain globals that depends on our site specific environment we do have a problem to solve. ;) > As I pointed out, some > frameworks don't make that possible. FWIW, there is some interest for > future Django to make it so you can host multiple sites within single > Django instance. If that happens then would be pretty cool as > currently Django sites need to be in separate sub interpreters or > processes which as you point out uses more memory. > > BTW, are you using custom web code, or using one of the major frameworks? Yes, we use our own web code. Django was a candidate - but it did not offer enough core features especially in the area of localization. None of the frameworks did - so we ended up writing our own custom CMS. And actually with the restrictions of Django that you mention above I am actually very happy that we didn't extend/adjust Django ;) Jan-Eric -- 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.
