Well aren't private reply blips sent on a brand new wavelet? It would seem that a robot would simply need to send a private blip with the poker hand to each player and then use a community blip for betting, etc. Are there currently API restrictions for private blips(I haven't needed the functionality so haven't been researching)? If so, I'm sure they will rectify that in the future.
On Oct 25, 2:01 pm, David Nesting <[email protected]> wrote: > Anything sent via state changes to the wave is visible to everyone. You > could do either of the following: > > 1. Use a gadget that communicates directly with your app to discuss the > "sensitive" aspects of your gadget/app (which cards the user was given), and > the server-side app would then be the exclusive authority. > 2. Communicate via state changes to the wave, but use encryption and > signatures to hide the content of the messages from other wave participants, > until the key can be released (allowing everyone to see and agree upon the > "winner"). > > David > > On Sat, Oct 24, 2009 at 1:49 PM, Wilfried > <[email protected]>wrote: > > > > > > > I understand that the approach of Google Wave is to collaborate on the > > same content but is it possible to display different content to the > > users on purpose? As an easy example, would it be possible to > > implement a Seafight or Poker type of game where I see a different > > playing field than my oppopnent(s)? > > > If so, is it possible to make this safe? Content coming from server/ > > robot side and what the user doesn't need to know is not transmitted? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
