Yeah, I realized there was going to be no way of saving on the bandwidth usage (a factor of magnitude more than processing power) by either doing cron (polling with data I don't need) or by just ignoring the keystrokes.
So I am going to have to just process on blip submitted, unless there is a way I can change the messages I want to get at run time (is there?). That way I could just process the first few, and then fall back to only blip submitted for larger edits. It also sounds like cron jobs do not give you access to current state, so that's a bust for that reason as well. Thanks for the suggestion though! Alan On Oct 31, 8:46 am, David Nesting <[email protected]> wrote: > On Tue, Oct 27, 2009 at 10:21 PM, voidref <[email protected]> wrote: > > For my syntax highlighting bot, I want the highlighting to be while > > typing is happening, however getting a notification on every character > > input will be a serious problem for bandwidth and processing. > > I don't believe you'll receive events for literally every character, but > you'll receive them often. I don't believe there's a way for your robot to > see updated state about a blip without handling these events. You can save > on the processing requirements, though, by ignoring a document_changed event > if you've just done one recently (in the last few seconds?). Handle > blip_submitted as well to ensure you didn't miss the last update to the > blip. > > On Tue, Oct 27, 2009 at 11:37 PM, Austin Chau (Google employee) < > > [email protected]> wrote: > > Cron job can recreate the blip context. Check out the sample robot Stocky. > > It persists wave, wavelet and blip IDs, so that the cron call can later > > recreate the context. > > This doesn't seem to meet the requirements of the original poster: it sounds > like he wants a way to access the *current* state of the blip, not the state > that the blip was in the last time the robot saw it (when it got persisted > to local storage). Stocky does not need to see the current state of the > blip in order to make its changes. > > David --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
