On Tuesday 27 Nov 2012 07:04:43 Jim Fulton wrote:
> Actually, it is. zope.server is based on asyncore.
> Having said that, my impression is that web sockets is largely (or
> completely) orthogonal to WSGI and the HTTP-based publishing
> infrastructure.

>From the RFC:

   The WebSocket Protocol attempts to address the
   goals of existing bidirectional HTTP technologies in the context of
   the existing HTTP infrastructure; as such, it is designed to work
   over HTTP ports 80 and 443 as well as to support HTTP proxies and
   intermediaries, even if this implies some complexity specific to the
   current environment.  However, the design does not limit WebSocket to
   HTTP, and future implementations could use a simpler handshake over a
   dedicated port without reinventing the entire protocol.  This last
   point is important because the traffic patterns of interactive
   messaging do not closely match standard HTTP traffic and can induce
   unusual loads on some components.

> ZTK is only relevant to the extent that it's a bag of useful libraries
> maintained
> by the Zope community.

It is a bag of useful libraries :) Is there anything that would ease the 
development of a WebSockets server, though? I would have thought there is, and 
that it would be at least possible, if not simple, to implement from existing 
base classes...

Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope )

Reply via email to