Allow disabling ping/pong?

It would be nice if a 0 value for pingInterval or pingTimeout could disable ping/pong checking entirely.

When used with an abstraction layer like Primus, the ping/pong is redundant and can sometimes cause situations where engine.io terminates the connection and Primus doesn’t pick up on it. In those cases Primus might not reconnect.

[STRML]

This is something we’ll have to be prepared for in every browser - Safari has been doing this for years, Chrome is next and I’m sure FF and IE are not far behind. We simply can’t rely on client timers being anywhere near reliable. I’ve seen 130+ (!) delays in Chrome 56. Word from them is that they will set a max, but the writing is on the wall.

On Jan 22, 2017 3:28 PM, “Luigi Pinca” [e-mail] wrote:

Yes, but the client timer that sends the ping is delayed by the browser so the server incorrectly closes the connection. Imagine that you used setTimeout(sendPing, 20000); on the client. The sendPing callback is not actually called after 20 sec but after 40 sec.

Hope it makes sense 😃

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/socketio/engine.io/issues/312#issuecomment-274361089, or mute the thread https://github.com/notifications/unsubscribe-auth/ABJFP9A_SydFX0hUCYKgTSZY1IZojB5Uks5rU8npgaJpZM4Dp2fJ .

[lpinca]

Yes, but the client timer that sends the ping is delayed by the browser so the server incorrectly closes the connection. Imagine that you used setTimeout(sendPing, 20000); on the client. The sendPing callback is not actually called after 20 sec but after 40 sec.

Hope it makes sense 😃