Re: WebSocket options?

Israel Brewster <[email protected]>
writes:

> 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.

I definitely use ws4py in production and haven't had any notable issues.
I did need to expend some energy to ensure that handling lost and/or
disconnected sessions was robust, but nothing that I felt was an issue
with ws4py, just the nature of WebSockets in general (or rather to be
fair, any long-lived socket approach).

I have no experience trying to mix with cpstats, but is there actually
use for cpstats on URLs on which you are using WebSockets - I wouldn't
think it would make much sense.

So what happens if you just ensure you don't have any URL where you
overlap both tools?  I'd think the only URL that needed the WS tool (and
not the cpstats tool) would be the one where you handle the transition
to the WebSocket.

-- David

-- 
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.