I’m attempting to create a “long-lived” gui (pyqt) client that can do repeated cycles of [connect / authenticate / do stuff / disconnect]. There is an excellent pyqt / autobahn example for the “gauges” demo that uses ApplicationRunner, but it does not authenticate so it doesn’t need a customized ApplicationSession like the authentication examples do. In looking at the autobahn.twisted.wamp module, it appears that the Application class is recommended ("… a simple way of creating, debugging and running WAMP application components.") – however, all the authentication examples simply create ApplicationSession instances and run them using ApplicationRunner. Application uses the special _ApplicationSession class to create its sessions – what would be the recommended practice for using Application with a subclass of ApplicationSession that does an authentication dance … override the Application.call method and use the subclassed ApplicationSession instead of _ApplicationSession?