Hi Brian, thanks for the response.

Could you clarify what you mean by "robots can only update a gadget's
state one time"? Do you mean once per processEvents(RobotMessageBundle
bundle) invocation?

Also, can you let me know if this throttling is a point-in-time
limitation or a design constraint? Based on your response I'd guess a
point-in-time limitation but I'd like to confirm so I can design
appropriately short-term and long-term. Also, if it's point-in-time it
would be good to know when you expect the limitation to go away so I
can determine if I tolerate the resulting problems or invest time in
workarounds.

By the way, based on the observed behavior and your response I had
another idea for a workaround. I haven't tried it yet but I'd be
curious to see what you think. Since client-side wave.getEvent
().submitDelta() changes seem to always result in (eventually)
callbacks to the onStateCallback function, I could simply create a
"ping" service (implemented with setInterval) that updates a
meaningless field (e.g. lastPingTime) every couple of seconds to make
sure onStateCallback gets called with the most recent information (my
onStateCallback function is idempotent so this shouldn't be a
problem). Does this seem like a reasonable workaround? I'm still a bit
new to wave programming so I'm never sure if a design idea is a good
one, a terrible one, or in between :-)

Thanks again,
BIll

On Sep 9, 3:19 am, "Brian Kennish (Googler)" <[email protected]>
wrote:
> On Tue, Sep 8, 2009 at 11:36 PM, Bill Higgins <[email protected]> wrote:
> > Hi, I'm creating both a robot and a gadget, and the two communicate by
> > the gadget's state object. However, I'm having a bit of trouble
> > because it seems like sometimes the robot sets gadget state on the
> > server-side but this isn't reflected in the client side.
>
> Hey Bill, as of last week, robots were limited to updating a gadget's
> state one time (the workaround being to delete the gadget and reinsert
> it). We had a pending change that undoes the limitation, but I'm not
> sure it got rolled out this week.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to