Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

seperating locking and messages backend? #62

Closed
bastianh opened this issue Jan 4, 2016 · 2 comments
Closed

seperating locking and messages backend? #62

bastianh opened this issue Jan 4, 2016 · 2 comments

Comments

@bastianh
Copy link
Contributor

bastianh commented Jan 4, 2016

I wonder if it makes sense to seperate the locking and messages backend. I think if you would want to use rabbitmq for example for messages you might still want to use redis or memcache for locking?
@andrewgodwin
Copy link
Member

Yes, I've already removed locking from the ASGI spec; I'm going to try and implement it directly on the sessions backend for starters.

@andrewgodwin
Copy link
Member

Locking is now gone completely, and replaced with enforce_ordering, which uses sessions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bastianh @andrewgodwin