Random thoughts about including Google Wave in your data flow
Like every other early adopter it seems, i’ve been noodling with Google Wave once my invite appeared in my developer sandbox account and I’ve been thinking/brainstorming ideas with Chris and Ken. It seems that like everything that is Web 2.0 a wave document can be both an data source and sink – processes need to be aware of this point lest a wave document just become another blog/log/journal endpoint.
What I mean is that since a wave document is an ever changing entity, any bot attached to a wave has the amazing chance to both deliver updates to the wave and also to receive updates (commands?) from the wave and I think most early bots are just doing the former.
Tags: palala, technology, wave
2. October 2009 at 14:34
That Python/Ruby/Perl #Wave bot is pretty interactive!
2. October 2009 at 14:55
Very interactive indeed. And that's a great example of how a bot/extension can be both a sink and a source, that bot probably treats all incoming change requests as discrete/atomic updates – i'm more worried about when a bot is present in 50 wave documents and it's getting 2/3 updates per document and *some* of them need to be distributed to something other than the source doc.
2. October 2009 at 18:34
That Python/Ruby/Perl #Wave bot is pretty interactive!
2. October 2009 at 18:55
Very interactive indeed. And that's a great example of how a bot/extension can be both a sink and a source, that bot probably treats all incoming change requests as discrete/atomic updates – i'm more worried about when a bot is present in 50 wave documents and it's getting 2/3 updates per document and *some* of them need to be distributed to something other than the source doc.