@Linc: The problem is not the CPU or how much I send back (already done that optimization), it's that on every DOC_CHANGED it sends a very large amount of data over, wether I use it or not.
This won't be a problem when I can put my bot on my own site, it's just a problem for the google apps limited free bandwidth. What would be ideal is if I could get a delta instead of all the text and all the annotations sent over. What would also be ideal is if there was a client side api in javascript I could use that mirrored the bot api somehow. Or Client Side Bots! @antimatter, yes, also an issue @Trejkaz, that would also help On Nov 1, 8:25 am, antimatter15 <[email protected]> wrote: > Or maybe the issue is that you are getting DOCUMENT_CHANGED events > even when the blip doesn't have code in it. > > On Nov 1, 7:23 am, Trejkaz <[email protected]> wrote: > > > > > On Sun, Nov 1, 2009 at 10:25 PM, Linc <[email protected]> wrote: > > > > Why not implement a counter or sth. so that you only react on everey > > > 3rd DOCUMENT_CHANGED. > > > Or some kind of capability saying that it only wants updates once > > every 3 seconds, and however many changes occur within those 3 seconds > > does not matter. I think that would be clearer, and you'd get a > > better idea of how many requests the app will be hit with (once per 3 > > seconds per subscribed wave?) > > > TX --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" 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/google-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
