Okay here's what I know: * Persistance - from the FAQ, I notice that persistance has not been > implemented. So when the server is restarted, waves are lost. Is this > still the case? >
Right now persistance has not been implemented for wave storage in the main repo. It's being implemented for user authentication and there is work on bring Anthony Watkins mongodb patch up to spec with the new WIAB paradigm. > > * Active API / Data APIs - I have specific uses for both the Active > API and the Data API. I have a prototype running against the sandbox > which is great, but I'm unsure if WIAB is ready for me to migrate to > using a hosted instance. Any ideas on this? > Lennard has already covered this. > > * Authentication - What's the current state of this? Both how an end- > user would authenticate against my application, and server-server > authentication. > In terms of user authentication, this is being worked on by Joseph Gentle. As mentioned above work is being done to utelise persistance and it's starting to come together. > > Also - just a general question regarding the timescales of my > application. Realistically, do you think WIAB is ready for production > quite yet, or do you think a delivery deadline of the end of this year > is unfeasible if I'm planning to work with WIAB as a core technology? > In order to achieve that deadline, we'd probably need WIAB to be as > complete as it's going to be by early November, and I'm currently > unsure if this is doable. > > Right now WIAB is not ready for production use however I think we could have something approaching that either by the end of the year (especially if more people jump on board). Certainly early in the new year. James -- 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.
