Jeez please no. I can't think of a more negatively branded product. The are very few products you could get away with branding "smoker".
This is exactly the point, bringing an unrelated personal interest into branding is exactly the mistake that happened in the first place. I think given the history, it is better off with a says what it does on the tin name. I think "wave in a box" is a stepping stone anyway. The conversational model is great, however in the future I think the way you interact on derivative systems in the future, to be something that is distributed in a federated way and self defining. There are many good ideas to come and this is not it by a long shot. I think it is going to go way beyond the existing extensions capabilities to full blown app docs that can be related to one or many waves. Wave is sort of in the same league as the internet or the telegram. So therefore there are some thing you can still learn from the web. RPC whilst great has some limitations. Browsers have client code (javascript) for a reason, with all it niggles it gets the job done and quite fast. There is no reason why you couldn't treat wave servers and client in the same sandboxed way and distribute agents in that way, it order to get fast automation for certain tasks. Other than that you should be able to take any cloud based app interface (such as gooogle docs) decouple in and connect it to a wave data store in a pain free way, and expose it to an API that linked to anything else related. -- You received this message because you are subscribed to the Google Groups "Wave Protocol" 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/wave-protocol?hl=en.
