HTTP Longpolling times out after 1 hour

[relu91]

Current implementation of HTTP long polling mechanism times out after 1 hour if no data is set after 1 hour. During the weekly call, we draft a few options:

• Automatic reconnect if it gets a timeout. @relu91 it might be hard to understand when it is a timeout due to inactivity or for other network failers
• Make the timeout configurable: it is hard to properly set the timeout when the use case is not clear
• Leave it as it is and let Applications handle it.

[hidetak]

Automatic reconnect if it gets a timeout. @relu91 it might be hard to understand when it is a timeout due to inactivity or for other network failers

In the case of an expected timeout, I believe that the server can prompt the client side to reconnect by returning a specific status code or message.
My apologies if my thoughts are not sufficient.