Graham Dumpleton
grahamd at dscpl.com.au
Sun Sep 5 01:15:49 EDT 2004
On 03/09/2004, at 11:15 PM, Michael C. Neel wrote: > Considering that all entries will be run under mod_python, and that > mod_python can setup custom interpters and namespaces/module > directories > per vhost, I don't see any reason they can't live on one host. Does > someone's framework *not* run under mod_python 3 / Apache 2.0 / python > 2.3? My bigger problem would be that I use mod_python as a front end only. That is, the application is not embedded within mod_python but would run in a separate set of processes which mod_python content handlers communicate to across a messaging system. The first problem is whether within the context of setting stuff up under SourceForge, whether one even has the ability to run separate processes. The second problem is that the messaging system support is built on top of C++ code. Thus, there would be a need to be able to build the C++ code and Python wrapper module and be able to install it within the SourceForge environment. If I know the correct host type, it can be compiled on the SourceForge compile farm, so would be more concerned about the first issue. I do have my own hosting site, but the mod_python on there is a bit broken because when they linked apache, they didn't link against reentrant libc.a with thread library functions. Thus not possible to build mod_python with thread support and thus cannot use messaging system which requires threading. Only other option is for me to start hosting off my home machine. -- Graham Dumpleton (grahamd at dscpl.com.au)
|