Yes, there will be consideration into how state changes affect (or, don't affect) playback when we design the revision to the Gadgets API.
On Sun, Dec 20, 2009 at 9:26 AM, Dan <[email protected]> wrote: > I believe there are plans to introduce alternative State changes for > cases like this. See > http://code.google.com/p/google-wave-resources/issues/detail?id=555, > for example. > > It's certainly a common problem to have waves always marked as > "unread" in all the participants' inboxes when, in fact, some > irrelevant minor change has been stored by a gadget. The fact that > these kinds of changes, which might routinely run into the thousands, > are recorded to playback as well is something I hope will be taken > into consideration when the alternatives are implemented. > > -- > > 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. > > > -- 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.
