Ideally, I would like an event that only gets triggered on a text change. The reason being that my robot currently gets a lot of resubmitted blips because of a gadget in them being clicked on. They can contain a lot of text which is still the same and has been seen by the robot. This eats up both the App Engine quota and processing time unnecessarily.
By adding a new event to trigger on text/(annotation?) changes it would ensure backward compatibility too. Combined with the new GADGET_STATE_CHANGED event this would allow the splitting of processing text or gadget but not both at the same time. On Nov 12, 1:53 am, "Austin Chau (Google employee)" <[email protected]> wrote: > Thanks for filing this. We will look into this. > > Austin > > On Wed, Nov 11, 2009 at 7:15 AM, César Izurieta > <[email protected]>wrote: > > > > > I'm developing a robot that sends an email every time it receives a > > BLIP_SUBMITTED event. It all works just fine except when there are > > gadgets on the page that change the state. Some gadgets change the > > state very often. For any state change google wave fires a > > BLIP_SUBMITTED event and the robot sees this as a new message and > > sends an email. Some gadgets (especially games) change the state with > > a very high rate. Besides the BLIP_SUBMITTED the DOCUMENT_CHANGED > > event and (sometime in the future) the GADGET_STATE_CHANGED are also > > being triggered. > > > My question is then: Does it makes sense to fire the BLIP_SUBMITTED > > event when a gadget changes it's state? > > > I think it should not. I've open a new issue here: > >http://code.google.com/p/google-wave-resources/issues/detail?id=422 > > but I would like to hear others what they think about this. > > -- 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=.
