Hi,

What is the problem that your’e trying to resolve with middlewares and why you 
think that you can’t use defaults as is?


> On 2 Aug 2017, at 14.59, Robert Stepanek <[email protected]> wrote:
> 
> I am new to Django and my project consists of two apps: a typical blog-style 
> web site app and an API app. For the latter, I do not need the majority of 
> middleware that is configured by default. Yet, I can't figure out what's the 
> best approach to use the default middleware stack for the web site app, but 
> not for the other.
> 
> If I understand correctly, the Django middleware layer does not take into 
> account which app a view belongs to.
> 
> Approaches that come to my mind are: 
> 
> 1. Define only the common subset of middleware that's used by both apps in 
> the project settings. And define a custom middleware class (e.g. 
> WebPageMiddleware) that combines the bunch of web-site related middleware 
> functions. Then decorate each view in the web site app with this aggregate 
> middleware. The problem I see with this approach is that I would have to 
> replicate the middleware stacking logic that's already handled somewhere in 
> the Django codebase? And it just takes one time to forget adding the 
> decorator to miss a bunch of critical protection middleware.
> 
> 2. Use two Django projects, one for the web site and one for the API app. 
> That would cleanly separate the settings but it would mean I have to take 
> care of two deployments (probably even a good thing).
> 
> Most probably there is a simple solution, but being a Django noob I must just 
> not be able to see it?
> 
> Thanks!
> Robert
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> To post to this group, send email to [email protected] 
> <mailto:[email protected]>.
> Visit this group at https://groups.google.com/group/django-users 
> <https://groups.google.com/group/django-users>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/3a1724c4-d24d-410f-9cc3-2675f7f0acb7%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/django-users/3a1724c4-d24d-410f-9cc3-2675f7f0acb7%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/FE726580-DC31-4FF2-A125-78B4A31B7C13%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to