#15089: contrib.sites and multitenancy
-------------------------------+------------------------------------
Reporter: legutierr | Owner: apollo13
Type: New feature | Status: new
Component: contrib.sites | Version:
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by akaariai):
I agree that thread-local sites would make sense in many use cases. I
think the whole Site model should be swappable. Then, there could be
Site.get_current_site() method by which you can alter what is returned
from that method. The default implementation returns site by
settings.SITE_ID, but if you use a swappable model, then you can alter the
implementation as you wish (middleware + thread-locals is a likely
approach here...).
--
Ticket URL: <https://code.djangoproject.com/ticket/15089#comment:46>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
For more options, visit https://groups.google.com/groups/opt_out.
