Client-side WebSocket options

#1

Hi! I have deployed a new Crossbar router installation and configured WebSocket options as described on its docs. But all of these options are server-side. For example, I want to WAMP clients to ping WAMP router automatically and drop related TCP connection when router didn’t respond. How I can configure WebSocket ping/pong parameters in WebSocket clients using CrossBar’s WebSocket transport?

0 Likes

#2

Hi!

As I understand it, this is a client-side issue, and so depends on the WebSocket client library that you are using.

Regards,

Alex

···

Am Donnerstag, 6. Dezember 2018 10:42:41 UTC+1 schrieb vladimir....@gmail.com:

Hi! I have deployed a new Crossbar router installation and configured WebSocket options as described on its docs. But all of these options are server-side. For example, I want to WAMP clients to ping WAMP router automatically and drop related TCP connection when router didn’t respond. How I can configure WebSocket ping/pong parameters in WebSocket clients using CrossBar’s WebSocket transport?

0 Likes

#3

I’m using CrossBar’s default ApplicationRunner class and it doesn’t set client WebSocket parameters.

···

четверг, 6 декабря 2018 г., 18:43:45 UTC+3 пользователь Alexander Gödde написал:

Hi!

As I understand it, this is a client-side issue, and so depends on the WebSocket client library that you are using.

Regards,

Alex

Am Donnerstag, 6. Dezember 2018 10:42:41 UTC+1 schrieb vladim...@gmail.com:

Hi! I have deployed a new Crossbar router installation and configured WebSocket options as described on its docs. But all of these options are server-side. For example, I want to WAMP clients to ping WAMP router automatically and drop related TCP connection when router didn’t respond. How I can configure WebSocket ping/pong parameters in WebSocket clients using CrossBar’s WebSocket transport?

0 Likes