That sounds great. I'd very much like to see an SQL-backed storage implementation. I have some experience and ideas about how to do it, so if/when you get round to designing it perhaps I can help.
Alex On 1 December 2010 12:02, Michael MacFadden <[email protected]>wrote: > Thanks for your thoughts. I am not sure exactly when I might start > working on this, but I think there is at least enough interest to put > it on the list of things to be done / looked in to at some point. > Thanks. > > On Dec 1, 1:50 am, Chris Harvey <[email protected]> wrote: > > FYI, the iotaWave server is built purely on a MySQL database, accessed > via > > JDBC from Java. This has allowed us to tightly integrate the wave-related > > tables (blips, waves, wavelets, threads, deltas, etc.) with all of the > other > > eMail and business functionality that we support. > > > > The high-performance requirements of Wave operation requires some thought > as > > to database schema design, especially indexing. > > > > -- > > Chris > > iotawave.org > > Singapore > > -- > 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.
