Essentially you can think of event handler/context as callback (endpoint)
with data (context). Imagine you have a handler for a particular type of
wave event. When that event has occurred, the Wave server could trigger
your endpoint with this notification. Associated with this notification, is
Aha! The light dawns.
On Oct 26, 4:40 pm, Austin Chau (Google employee)
api.aus...@google.com wrote:
Essentially you can think of event handler/context as callback (endpoint)
with data (context). Imagine you have a handler for a particular type of
wave event. When that event has occurred,
On Mon, Oct 26, 2009 at 1:31 PM, Chris C. yclept.ch...@gmail.com wrote:
Okay, I've written a robot that parses new blips for particular
strings (in this case, strings representing dice rolls), and inserts
the result of a particular dice roll in the blip. It works fine,
exactly as I expect
No you have no control context. Context is managed sent by the server. If
you need to maintain states, you need your own datastore or you can use the
DataDocument from Wavelet.
