-
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
server, opened() is called each time a message is send #162
Comments
Indeed, it should only becalled once when the connection was created. That is weird. Which versions of CP/ws4py are you running? |
CherryPy==3.6.0 The purpose of the code is: for a school class. I maintain a client for scratch, which allows for hardware access on raspberry pi. This code has an embedded web server to display current configuration and some events. The code is derived from the Echo-Sample. But I use the RoutesDispatcher. [code]WebSocketPlugin(cherrypy.engine).subscribe() animationHandler = AnimationHandler() dispatcher.connect(name='adapterAnimation' , route='/ws' , controller=animationHandler , action='ws') [code] [code]
[/code] |
I've never tried ws4py with the RoutesDispatcher so I'm wondering if there isn't some sort of corner case with that dispatcher. How many times do you the log from the ws4py manager: Managing websocket ... ? |
ws4py - 243 - INFO - Managing websocket [Local => 127.0.0.1:8080 | When terminating connection (by closing client web page), I get Looks strange. On 06.04.2015 19:23, Sylvain Hellegouarch wrote:
|
I must say I'm a bit puzzled honestly. I can't figure out where the opened() method could be called elsewhere. So, it could be a thread issue but I fail to identify it :( |
Found the problem in my code (better: in front of my computer). Thank you for your support ! On 07.04.2015 13:18, Sylvain Hellegouarch wrote:
|
Well... that's a relief. Enjoy! :D |
Using websocket with cherrypy.
Whenever I pass a message from client to server, the server's opened-method is called.
I assume that this method should be called only once per successful connection.
The text was updated successfully, but these errors were encountered: