Open oberstet opened 5 years ago
rgd Autobahn at the WebSocket level, and on Twisted:
listenWS
: https://github.com/crossbario/autobahn-python/tree/master/examples/twisted/websocket/echo_tlssidenote: wading through our examples etc, I recognize this is quite hard to navigate (lots of variants etc). likely very hard or impossible for beginners. on the one hand, the large number of variants is inevitable, as Autobahn simply supports running on a lot of flavors, but on the other hand, we should provide better guidelines of what to use when. well. a day tocks in only 24 hours;)
the ssl: client endpoint doesn’t work with IPv6, and the tls: endpoint does.
https://twistedmatrix.com/documents/current/core/howto/endpoints.html
mmmmh. not sure: does that mean that a regular TCP v6 twisted endpoints now also works for TLS?
So we want to support IPv6 in Autobahn - for all flavors. This is not the case as of today (see below).
Longer term, the "flavors" we need to cover are:
autobahn.twisted.websocket.listentWS
andconnectWS
) and "new API" (using Twisted endpoints)ApplicationSession
) and "new API" (Component
)I have quickly looked at the status of Twisted and Twisted endpoints relating to above (I haven't analyzed all the others).
Twisted endpoints is the "new" and recommended API of Twisted, and it supports TCP v4+6, but only TLS v4 on Twisted 18.9.0:
Autobahn is using above here to create client connecting transports.