Javascript? If there is uptake of the "doodad" then it federated merely by being distributed, by federated means.
Basically you have in effect a form of distributable agent code. Which is something I have been calling for since robots are inherently slow and limited. So you could come up with your own spelly or rosie for instance. However I don't think it has to be in a blip, although that would work. Why not allow it to be it outside of the conversation doc? as I have said countless times conversations are just a default form of communication that grated will be popular amongst others. You should put automatic restrictions. Like public via proxy is added at the start by the owner. I also think distributable agent code could be used give the server itself instructions. This would work with the public via proxy group/ permission, which would allow any form access control and other interaction requirements via public via proxy moderation, negating the need to countless predefined permissions. I see the limitation of iframes and opensocial. However I think eventually three need to be a full-blown wave application framework that covers hooking up doc apps (the size of the big cloud based app coming up now not quirky gadgets), and their doc to the wave platform, as well as other automation agents and interactions. So this dodad I don't think is elegant solution but it is a start. I think can learn from opensocial and caja and other ideas. On Dec 2, 1:56 am, Chris Harvey <[email protected]> wrote: > What are the implications of inserting "third-party Javascript into a blip" > from a federation viewpoint? > > I may be missing something in my thinking here but won't the WFP handle that > code simply as "blip content" and therefore a second (federated) wave server > be a bit confused when it sees that code (and thence simply display it as > "plain text")? > > -- > Chris > iotawave.org > Singapore -- 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.
