Thanks Lennard, That's really help. Your subsequent message was also really useful to see what's been implemented, and what is still missing.
> What are your needs? Is it a university project or a real business application? It's a real business application, for internal use only with a limited set of users. However, the deadline is fairly fixed. We're currently evaluating whether or not we're safe to use WIAB, or whether it's too much of a risk to proceed at this stage. Thanks again, Toby On Wed, Oct 13, 2010 at 11:47 AM, Lennard de Rijk <[email protected]>wrote: > Hi Toby, > > I'll just respond on my area of expertise (robots), the rest will be picked > up by the others. > > On Wed, Oct 13, 2010 at 8:16 PM, Toby <[email protected]> wrote: > >> 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? >> > > The Active API and Data API plumbing is implemented, meaning that the > server has endpoints for receiving messages from a robot. However most of > the operations and events(for the passive API) are yet to be done, see also > [0]. More events and operations are becoming available every week and if you > need something specific it should be fairly easy to send in a patch for it, > feel free to ask us for pointers. > > >> * 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. >> > > What are your needs? Is it a university project or a real business > application? > > Greetings, > Lennard > > [0] > http://groups.google.com/group/wave-protocol/browse_thread/thread/aee34a503d25f9e > > -- > 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]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > -- 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.
