[Google Wave APIs] Re: Fundamental question - what does context...um...do?
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 the context data that are sent along with it. So that in your handler, you can actually retrieve the plain text data of the blip. Austin 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 and desire. I see in the tutorial that there is something called CONTEXT in the API. So here's the question: what does that do? What additional capabilities does that provide to a robot? Thanks! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Wave API group. To post to this group, send email to google-wave-api@googlegroups.com To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en -~--~~~~--~~--~--~---
[Google Wave APIs] Re: Fundamental question - what does context...um...do?
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, the Wave server could trigger your endpoint with this notification. Associated with this notification, is the context data that are sent along with it. So that in your handler, you can actually retrieve the plain text data of the blip. Austin 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 and desire. I see in the tutorial that there is something called CONTEXT in the API. So here's the question: what does that do? What additional capabilities does that provide to a robot? Thanks! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Wave API group. To post to this group, send email to google-wave-api@googlegroups.com To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en -~--~~~~--~~--~--~---
[Google Wave APIs] Re: Fundamental question - what does context...um...do?
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 and desire. I see in the tutorial that there is something called CONTEXT in the API. So here's the question: what does that do? What additional capabilities does that provide to a robot? On Mon, Oct 26, 2009 at 3: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, the Wave server could trigger your endpoint with this notification. Associated with this notification, is the context data that are sent along with it. So that in your handler, you can actually retrieve the plain text data of the blip. Is it possible to add data in there (I mean robots adding data ...) to be used later by the robot ? For example, I'd like to implement a robot that infers some data by analyzing the text of the blips, and I'd like to stores this (meta-data | state info) in order to use it later inside the same wavelet, to transform or create other blips. It's semantics are specific to the robot behavior, probably not to any robot compatible with Google Wave API . Is this possible or context is just about (visual | core) aspects of the system ? Thnx -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: Suggestions: Wave (private) Groups, integration - Google Wave API ... - http://feedproxy.google.com/~r/TracGViz-full/~3/cuwdwGkX1WA/90bf35ca0c38caf0 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Wave API group. To post to this group, send email to google-wave-api@googlegroups.com To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en -~--~~~~--~~--~--~---
[Google Wave APIs] Re: Fundamental question - what does context...um...do?
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. http://wave-robot-java-client.googlecode.com/svn/trunk/doc/com/google/wave/api/Wavelet.html#getDataDocument(java.lang.String) Austin On Mon, Oct 26, 2009 at 2:03 PM, Olemis Lang ole...@gmail.com wrote: 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 and desire. I see in the tutorial that there is something called CONTEXT in the API. So here's the question: what does that do? What additional capabilities does that provide to a robot? On Mon, Oct 26, 2009 at 3: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, the Wave server could trigger your endpoint with this notification. Associated with this notification, is the context data that are sent along with it. So that in your handler, you can actually retrieve the plain text data of the blip. Is it possible to add data in there (I mean robots adding data ...) to be used later by the robot ? For example, I'd like to implement a robot that infers some data by analyzing the text of the blips, and I'd like to stores this (meta-data | state info) in order to use it later inside the same wavelet, to transform or create other blips. It's semantics are specific to the robot behavior, probably not to any robot compatible with Google Wave API . Is this possible or context is just about (visual | core) aspects of the system ? Thnx -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: Suggestions: Wave (private) Groups, integration - Google Wave API ... - http://feedproxy.google.com/~r/TracGViz-full/~3/cuwdwGkX1WA/90bf35ca0c38caf0 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Wave API group. To post to this group, send email to google-wave-api@googlegroups.com To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en -~--~~~~--~~--~--~---
