> Graham wrote something about one script per URL: > > http://groups.google.com/group/modwsgi/browse_thread/thread/fbda3f584...
yes, i recall the post and it was encouraging to see at least some potential in a one file per URL setup. In fact I started the thread asking about the feasibility of this design approach. Now that I've had time to think about how to configure this, I realized it would be nice if the usual requirements for a single WSGI application script file to display it's own templated content: - the explicit need for an application entry point. - the explicit need for a start_response function call. - the explicit need to return content. could be handled by additional configuration directives or rewrite rules or some other work-around and have reasonable default settings built-in, e.g. start_response status and header values. In the meantime, I'll look into emulating this design using WSGIScriptAliasMatch to map several template files to one WSGI application script file. -Walter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
