Hi,
I am not sure whether the current Python client API has already been
updated
but the one I used (downloaded end of Oct) for my bot only passed
context and
properties to the Handler and not the event.
I changed line 124 in waveapi.robot_abstract. Obviously, you will need
to adjust
your handler
And GADGET_STATE_CHANGED is not in current API neither in java nor
> > > python.
> > > Where did you found it ?
>
> > > On Nov 17, 1:02 am, hcvst wrote:
>
> > > > Hi,
>
> > > > my bot's capabilities.xml states that it is interested in
...@appspot.com,
restarting the browser
and adding participants.
Regards,
HC
On Nov 16, 9:02 pm, hcvst wrote:
> Hi,
>
> my bot's capabilities.xml states that it is interested in
> GADGET_STATE_CHANGED events. I've upped the bot's version after adding
> this event t
Hi,
my bot's capabilities.xml states that it is interested in
GADGET_STATE_CHANGED events. I've upped the bot's version after adding
this event to the ones it's interested in, yet looking at the GAE logs
my bot does not seem to be notified.
Is this event not supported yet?
Thanks,
HC
--
You re
I guess I'll use the robot events instead of an AJAX call. There does
not seem to be a reliable method to secure it.
HC
On Nov 12, 11:14 am, hcvst wrote:
> Hi,
>
> my gadget issues an AJAX call to remotely update some data when its
> state changes. The AJAX endpoint is the same
Hi,
my gadget issues an AJAX call to remotely update some data when its
state changes. The AJAX endpoint is the same server that hosts the
gadget.xml (Appengine). Currently, anyone looking at the gadget's
source can see the endpoint
and call it themselves with some query parameters to effectively
Hi Flavio,
let your bot add the gadget and include some query-string parameters
such as
the wave-id when it does, so that you can correlate in subsequent
requests on that
id.
I've used that approach for my wavedirectory.net. Source available at
github.
http://example.com/gadget.xml?waveid=id
Re
Hi Austin,
so cron works again? Last time I checked, my bot was never notified
and all
threads here spoke of cron not working for now (possibly until the new
mechanism
is rolled out).
HC
On Nov 9, 4:14 am, "Austin Chau (Google employee)"
wrote:
> We do not have documentation for the current cr
