On Fri, Aug 22, 2008 at 9:01 PM, Nimrod A. Abing <[EMAIL PROTECTED]> wrote: >> Thus, long running file uploads perhaps better handled in embedded >> mode, or delegate the URLs for file upload to special daemon process >> that doesn't recycle process so as to avoid problem with it being >> interrupted. > > That would require us to have a subdomain just for this purpose, I'm > predicting this will cause the Django authentication system to fail > somehow. But I will look into it and see if it's feasible.
Strike out that last bit. Just went through the Django docs and found it can be configured to use cross-domain cookies for sessions, so having a separate subdomain for file uploads is feasible in our case. Still curious about defaults for *-timeout values. Additionally, is it possible to specify multiple WSGIScriptAlias directives in one VirtualHost? How about WSGIProcessGroup, is it possible to specify more than one WSGIProcessGroup in one VirtualHost? This could allow the option in case subdomains are not feasible: WSGIScriptAlias URL-path file-path|directory-path [process-group] But that would require the ability to be able to define multiple WSGIProcessGroups and WSGIDaemonProcesses in one VirtualHost. -- Best Regards, Nimrod A. Abing W http://arsenic.ph/ W http://preownedcar.com/ W http://preownedbike.com/ W http://abing.gotdns.com/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
