And second problem with WebSockets implementation is that pingPeriod and timeout are not interrelate...

# ktor

[Nail Gilaziev]

And second problem with WebSockets implementation is that pingPeriod and timeout are not interrelated. Maybe I'm wrong... I must be wrong, please)

pingPeriod = Duration.ofSeconds(30) // Disabled (null) by default
timeout = Duration.ofSeconds(15)

When connection between client & server are unexpectedly broken(TCP not closed properly) I expect that an exception will thrown after maximum of 45 seconds.(ping period+*pong* response waiting timeout). But it not happens. What am I do wrong?
Should I independently implement this behavior through raw sockets?

[e5l]

Could you provide your message handling sample?

[Nail Gilaziev]

server:
https://gist.github.com/nailgilaziev/77b5b7c2f0cca140c643b29f077663e6
client:
https://gist.github.com/nailgilaziev/4ead4fa43274949529396db6bd3b3b60

[Nail Gilaziev]

when I specifically break the connection, the time after the server and the client throws timeout exception is always different. I met half a minute and three minutes and more.

[e5l]

Thank you, I'll take a look

[Nail Gilaziev]

with increasing or decreasing delay time for client code I tested throwing timeout exception by reasons:
* ping messages
* ordinary text messages

[Nail Gilaziev]

@e5l, hello! Is there any new information on this?

[Nail Gilaziev]

@e5l, I think you did not see the notification) can you answer?