Hi, You can probably do some of the behaviors you described by having your own scheme of in your state data. For instance, you adopt the format for your state data such that you would append the username before the actual value to indicate the data provider, ie [email protected]_data
This is not perfect, but in general a lot of things can be possible with a little bit more works, in the way how you send data and how you interpret and propagate data. Austin On Sun, Dec 6, 2009 at 11:59 PM, dougx <[email protected]> wrote: > I've been thinking about this for a while, and after reading a few > posts about it (eg. > http://groups.google.com/group/google-wave-api/browse_thread/thread/26fbe8c7862cab06/4900719e6e8e4e9f > ) > I think there's a use case for Gadgets which isn't being addressed. > > Basically, it comes down to this; > > Situtation: A number of people are involed in a wave with a gadget. > Action: A user changes the gadget. > Problem: No one knows who changed the gadget. > > You can write a good gadget such that each user posts to an event > register that the other gadget instances can see, and pull out the > event to see who made the change, and what change it was... but > there's no native api to assist with this, or ensure that that > transactions are accurate. One user could be faking it, pretending to > be someone else. > > This seems to be a problem for example for; > > - Gadgets where the state is updated but only some users may be > interested depending on who made the update. > > - Competative game gadgets, where users can gain an advantage by > faking their own high score. > > - Gadgets where users collaborate in general (prone to spoofing; even > on playback you can't really be sure of the changes being made coming > from the supposed author). > > The only method I'm aware of is to have a robot that sits and > constantly watches the gadget and does some kind of 'undo' action on > any state changes to the gadget which appear to be dubious. Seems like > a hard way of doing this... > > It'd be like robots only being able to see the current wave state, > without any other information when they got events. > > Am I missing something? Or is there really no way around this? > > ~ > Doug. > > -- > > 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]<google-wave-api%[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.
