Hi guys, I'm planning to use WIAB for a project which should be ready for the end of the year, and I'm hoping to get some advice from the group on whether this is realistic or not.
My project would involve a custom web-client to provide searching and filtering of waves, and a number of robots interacting with the waves when certain criteria are met. I'm finding it difficult to understand what has been implemented, and what has not. My particular areas of concern are: * 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? * 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? * Authentication - What's the current state of this? Both how an end- user would authenticate against my application, and server-server authentication. 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. Would be very grateful if anyone can shed any light on the above. Thanks in advance, Toby -- 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.
