Werzeug incompatibility about django-websocket-redis HOT 4 OPEN

I never used werkzeug, so I can't really say whats the problem.
You're encountering this problem in debug mode. There ws4redis hijacks the main loop if the URL starts with /ws. I assume that werkzeug somehow gets in conflict with this approach. Could you please dig into that direction.

from django-websocket-redis.

The problem is that werkzeug is using standard django WSGI handler from from django.core.handlers.wsgi import WSGIHandler, so if it's not overwritten then it fails. And I didn't found setting to do that without monkeypatching or editing source code.

It's working ok, but werkzeug is WSGI which isn't Async like websockets, so after keeping connection too long it just closing it forcefully. It event write you about it INFO: Finish long living response with status code: 192.168.85.1 - - [29/Jul/2014 22:04:57] "GET /ws/foobar?subscribe-broadcast&publish-broadcast&echo HTTP/1.1" 101

It's just incompatible. Use django-devserver witch allow to add option --wsgi-app=ws4redis.django_runserver or add such possibility to werkzeug :)

from django-websocket-redis.

@kosz85 were you able to successfully monkey-patch Werkzeug then?

from django-websocket-redis.

No I'm just using django-devserver. I think it's easier and less time consuming to use nginx with uwsgi or django-devserver then rewriting werkzeug. If this is not an option, you can try run two separate servers, one for websockets without werkzeug and second normal for django app with werkzeug. Thought such setup will need to add some changes to app (adding port for websockets or proxy like nginx).

from django-websocket-redis.