Module Middleware

Question

Though not documented, OSQA modules provide a rather flexible plug-in architecture for the application. OSQA modules can supplement the app’s URL structure, and provide additional startup code, views, templates, database models, and user authentication providers.

To provide even greater flexibility, I would like to suggest that OSQA provide the facility for modules to contain Django middleware classes. OSQA could implement its own ModuleMiddleware class, for example, which would find and delegate to any middleware.py files detected in OSQA modules.

The main use case I would have for this facility would be supporting automatic user logins based on the session cookie of another application running on the same domain, and for which I have already written an OSQA authentication module.

Accepted Answer

The code on trunk already does what you're looking for, just add a variable named MIDDLEWARE_CLASSES on the __init__.py file of the module, containing a list of your middleware, the only difference is that the path used should be relative to your module. So if you have mymodule, and a file named middleware.py, and inside a piece of middleware named MyMiddleware, the module __init__.py would contain the following:

MIDDLEWARE_CLASSES = [
    'middleware.MyMiddleware',
]

Module Middleware

Follow this question

Learn more about OSQA

Related questions