On Oct 5, 11:59 pm, "[email protected]" <[email protected]> wrote: > Another way to optimize things for the client would be detect an idle > client - that is, if the client is left open, just watching, but the > user has not had activity in a while, the client could reduce the > update rate and even signal the server to send fewer (larger) updates. > If this happened gradually, the user would not notice.
More importantly, this is something that can be taken advantage of on the clients of the other participants. If a client is idle (i.e. no user activity at all) for more than a few minutes, you can assume that the user is not near the computer. That's almost the same as if the user is offline, and thus not viewing the wave. So if you have e.g. 5 participants online, but 4 of them have been idle for a while, the 5th can reduce his update frequency as if he's the only one who's viewing the wave. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
