Why Setting A Client-side Timeout When Using Long Polling?
In almost every long polling examples I see, there is something like a timeout of 30 seconds client-side. What is the precise reason for this?
Solution 1:
Some routers, proxies or whatever device there is in the middle might decide to drop TCP/IP connections being idle for extensive period of time. Also refreshing connection once in a while makes sure you'll discover server failure quicker.
Post a Comment for "Why Setting A Client-side Timeout When Using Long Polling?"