#29846: Signals - handling multiple requests concurrently
-------------------------------+--------------------------------------
Reporter: anomitra | Owner: nobody
Type: Uncategorized | Status: closed
Component: HTTP handling | Version: 1.11
Severity: Normal | Resolution: invalid
Keywords: signals | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => invalid
Comment:
Hello there,
If you want to achieve this using a middleware you'll most likely want to
assign a thread local and use a single signal receiver to look it up but
that's usually considered a bad pattern because of the global state it
creates. While there's is third party apps implementing this pattern
you're better off passing along `request.user` from your views to your
forms/serializer and models instead.
Please use TicketClosingReasons/UseSupportChannels to help you figure out
the missing pieces of the puzzle as this issue tracker is used to keep
track of bugs and feature requests and isn't a second tier support
channel.
--
Ticket URL: <https://code.djangoproject.com/ticket/29846#comment:1>
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.9536372cc34b0aa75954133ad1648e70%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
