Re: WebSocket options?

The cpstats one is the only one I have posted as an "issue", since it is 
the only one I have been able to track down. You may be right that it isn't 
directly related to ws4py, but the fact remains that I can use cpstats, or 
I can use ws4py, but not both - ws4py dies with cpstats enabled. Nothing 
else does that I can see. That particular issue I posted on the issues 
list, this list, the ws4py list, and the general python mailing list - and 
got no responses to any of them.

Other than that, there is this message I posted the other 
day: https://groups.google.com/forum/#!topic/ws4py/cmeZHKd8ezg, and then 
there are the things I haven't actually posted about, since I found 
workarounds: The dozens of lines of javascript I've had to write to 
automatically re-open web sockets when the close, the monitoring code I've 
put in to figure out when the sockets (and the server itself) stop working, 
the fact that I've had to abandon trying to use the web socket to 
communicate from the client back to the server (I worked around that one by 
just doing standard HTTP calls, and tying in to the WebSocket class with 
function calls) because using the WebSocket itself for communications 
proved unreliable in production where I have dozens of sockets open, and 
the fact that since implementing sockets I have been having to restart the 
server every couple of days to clear out CLOSE_WAIT sockets and keep the 
server responsive. It's just been one headache after another. Before I 
started trying to use WebSockets, everything was rock-solid - I had the 
server running for over two weeks without an issue once (usually I restart 
more often than that for updates).

Given the response I did get to the message I mentioned above, I'm thinking 
the best option at this point is to use a completely different framework 
for the web socket portions of my code. I'll just have to figure out how to 
make the two systems talk to each other, but that should be manageable.

Thanks for the response.

On Wednesday, November 4, 2015 at 11:07:23 PM UTC-9, [email protected] 
wrote:
>
> WRT cpstats, I just found that, not sure if it that error is related to 
> ws4py, though: https://github.com/Lawouach/WebSocket-for-Python/issues/177
>
> On Thursday, November 5, 2015 at 8:57:36 AM UTC+1, [email protected] 
> wrote:
>>
>> That's strange, I haven't had that experience at all, things have been 
>> working well. I don't let connections stay open super long, but for a while.
>> Could you direct me to some of the issues you have created on the project 
>> that describes these issues? I can't find any of them?
>>
>> //Nicklas
>>
>> On Wednesday, November 4, 2015 at 11:40:42 PM UTC+1, Israel Brewster 
>> wrote:
>>>
>>> Are there any options for doing web sockets with CherryPy other than 
>>> ws4py? ws4py has way to many bugs for me to feel comfortable using it in a 
>>> production environment. I thought it would work well at first, but the 
>>> longer and more I try to use it, the more problems I run into. Connections 
>>> not remaining stable, communication only working one way, sockets winding 
>>> up in a CLOSE_WAIT state until the server is unusable, web sockets not 
>>> working at all if I enable cpstats, etc. Maybe if there was another option, 
>>> that would work better?
>>>
>>> Thanks.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "cherrypy-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cherrypy-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
To post to this group, send email to cherrypy-users-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
Visit this group at http://groups.google.com/group/cherrypy-users.
For more options, visit https://groups.google.com/d/optout.