-
Notifications
You must be signed in to change notification settings - Fork 289
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.
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
Threaded WebSocket client always exits randomly #78
Comments
Would you mind telling me which ws4py version you're running please? As for the droid example, I must admit that's one piece I haven't maintained well so if it's failing I'm not entirely surprised. |
Of course, here are the versions I use: |
Okay. May I ask you if you could try with the latest HEAD (0.3.0-beta) please? I've made some modifications that could help (or not ;)). |
That was a good idea: It seems to work now as expected! Edit: Despite the fact that the client is working, the server displays this error immediately after the client is started:
|
Damned! :) I'll probably need to test it out but that won't be before this evening at best. Sorry. |
I mean the client is running and the server keeps running too, except this exception appears in the server log as soon the client connects, so take your time ;) Thanks anyway sofar! |
I tried to implement a simple WebSocket client for a CherryPy server which should work like the droid_sensor.py and its server under "example", but if I try to run the client it always stops randomly in the send loop and exits with a random WebSocket error code (one of 1002, 1006 and 1007).
This is the server log from the CherryPy server:
This is my client (very similar to example/droid_sensor.py):
https://gist.github.com/muellermartin/4974648
and this is the server:
https://gist.github.com/muellermartin/4974657
P.S.: The host in line https://github.com/Lawouach/WebSocket-for-Python/blob/master/example/droid_sensor.py#L98 seems to be wrong (script crashes with
ValueError: Invalid scheme: http
) - shouldn't this be "ws://127.0.0.1:9000/ws"?The text was updated successfully, but these errors were encountered: