Actually, I'm quite interested in that... If the wave-in-a-box is going to support the data api, it'll have to support OAuth and a full user authentication stack; How is that going work?
I thought perhaps it might piggy back off shindig for that, but if the user authentication and oauth is left to the shindig instance, I can't quite see how the wave server is going to interact with that to offer the data api and login stuff. >From the start the reasons Fed1 wasn't really usable in the real world were: 1) No web gui (now we have splash, although it is read only..) 2) No persistence (yay, mongo db) 3) No user accounts .... Very curious how wave-in-a-box is going to address (3). Perhaps openid? ~ Doug. On Sep 4, 3:50 pm, Lennard de Rijk <[email protected]> wrote: > Hi Matt, > > On Sat, Sep 4, 2010 at 4:12 AM, Matt Richards <[email protected]> wrote: > > From what the blog says, it will not be the same as the current Google Wave > > Service.. > > I'd gather it'll lack the robot APIs, and potentally the embedding APIs but > > what else? > > Actually as the blogpost states we will work towards supporting the current > Gadget, Robot and Data API. > > About the embedding API this is what Pamela Fox had to say about it [0]: > > There is no plan to support embedding in the open source plan, but it should > > > be fairly straightforward for a developer to modify the code so that there > > is an output of the client that includes only the wave panel. (Our own embed > > API basically did that-- just hid all the other panels). > > Greetings, > Lennard > > [0]https://wave.google.com/wave/#restored:wave:googlewave.com%252Fw%252B... -- 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.
