On Mon, Oct 5, 2009 at 7:30 AM, Michael K <[email protected]> wrote:
> 6. Still on the client, only request real-time updates for a page when > it gets into view (or just below / above the view). Make sure to tell > the server you no longer need real-time updates for pages outside the > view. The client may update out-of-view pages at a lower frequency to > make sure they don't get too far out of sync. > > 7. If a wave is not being viewed by anyone else, send deltas to the > server less frequently to reduce message overhead and strain on the > server. Concatenate operations on the client before sending them. > > > These are just some ideas to get the discussion started. What else can > be done? > It would be nice if the client could inform the server that it only wants 'bursty' communication, and set the interval between transmissions, this would let clients/users optimize for their own environment. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
