-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WampSharp Monitor not sense router-side channel close #217
Comments
What router? |
The router is Python-based. I'm developing a multiplatform application so the router is on Ubuntu with Python and the client on Android is based on jawampa. |
The router is crossbario? |
Yes, the router is crossbar.io implemented with autobahn-python. ` WampChannelFactory factory = new WampChannelFactory();
|
You are using the WebSocket4Net implementation. It automatically sends ping messages every 60 seconds by default. See here. This mean that 60 seconds after the router gets down, WampSharp should detect this. Elad |
Oh, I see. Thank you. |
This will cost you by pinging the router every smaller interval. This can be achieved by providing you own WebSocket4NetFactory delegate to the first call. factory.ConnectToRealm("MyRealm")
.WebSocketTransport(subprotocolName => new WebSocket("wss://10.0.0.101:8443/ws",subprotocolName)
{
AutoSendPingInterval = 30
})
.SetSecurityOptions(options =>
{
options.EnabledSslProtocols = System.Security.Authentication.SslProtocols.Tls12;
})
.JsonSerialization()
.Build(); |
I've tryed this solution but it doesn't work. It still not sensing the channel closure router-side. |
Have you tried changing the AutoSendPingInterval value?
|
Yes, I also set AutoSendPingInterval to 1, but it doesn't work. I don't know why.. BTW, instead sensing the channel closure, can I sense the session killing router-side having also the killing reason? In other words can I have feedback on WampSharp client when the Autobahn-python router call all(u'wamp.session.kill', session, u'myreason', u'newuser')? |
AutobahnPython is not a router, it is a client library. Your router is crossbario. Elad |
Ok, but there is however the problem that ConnectionBroken event is not raised. When on crossbar.io router I call wamp.session.kill, jawampa sense the session killing but WampSharp doesn't do that. |
This should be solved with version 1.2.6.44-beta (released moments ago). Elad |
Thanks a lot for this immediate fix; I very appreciate it! Andrea |
The WampSharp monitor not sense the closure of the channel made router-side. Is there a way to sense it?
Thanks in advance.
The text was updated successfully, but these errors were encountered: