You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've just figured out some behavior of the Ember+ Viewer. It might be intended, but the VSM Studio behavior is different and I am not quite sure how to handle this situation.
The Ember+ Viewer sends a Keep-Alive message (if enabled) according to the specs every 4-5 seconds. But the timer is reset if there is a message send to the Ember+ Viewer. If I am sending messages periodically in less than 4 seconds, I will never see the Keep-Alive message and therefore close the connection at a certain point (whatever the timeout on our system is).
I am using the Ember+ Viewer v2.40.0.24, I didn't test the latest version yet. For the time being I'd to remove the timeout on our system, but usually we like to use it to handle situations where no proper TCP close is send by the clients connected to our system.
Best Regards,
Tobias Thierolf
The text was updated successfully, but these errors were encountered:
Hello,
I've just figured out some behavior of the Ember+ Viewer. It might be intended, but the VSM Studio behavior is different and I am not quite sure how to handle this situation.
The Ember+ Viewer sends a Keep-Alive message (if enabled) according to the specs every 4-5 seconds. But the timer is reset if there is a message send to the Ember+ Viewer. If I am sending messages periodically in less than 4 seconds, I will never see the Keep-Alive message and therefore close the connection at a certain point (whatever the timeout on our system is).
I am using the Ember+ Viewer v2.40.0.24, I didn't test the latest version yet. For the time being I'd to remove the timeout on our system, but usually we like to use it to handle situations where no proper TCP close is send by the clients connected to our system.
Best Regards,
Tobias Thierolf
The text was updated successfully, but these errors were encountered: