On Tue, 2009-10-20 at 21:00 -0700, Alf wrote: > Hello James, Hi
> Let me elaborate my original questions with more details. > 1. I'd like the Wave conversation originator to be able to change an > acces level to the Wave at some point in time, and do it as many times > as he or she wants to. At the moment not possible on either Google Wave or FedOne. ACL's (access control lists) are part of the future plans. > 2. I am looking to build my own service on top of the Wave. For the moment, I don't think there are any plans to release a direct Google Wave API (as in something similar to the Google Docs API). Once again I think your best bet here is to develop your own Wave infra using something like FedOne as a starting point. > 3. I'd like the Wave thread originator to be able to use Wave as a > blog engine, if he/she wants to (means - to provide public access for > everybody to the Wave). This is doable now via Robots and Gadgets. However again we are limited to those with Google Wave accounts. > 4. He or she should be able to use Wave as a very private blog, that > means he allows the access for himself only. See point 4 > 5. Also, I'd like the customer to be able making Waves accessible to > no one (including himself) for a certain period of time, even for the > lifetime period. See point 1 re ACLs > 6. etc. I hope that helps. -- James Purser Collaborynth http://collaborynth.com.au Mob: +61 406 576 553 Skype: purserj1977 Twitter: http://twitter.com/purserj --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" 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/google-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
