Personally if we're going to write a SQL driver, I think we're best of going with the most commonly installed db - MySQL. Most developers would have it installed, most hosting providers would have it and its a well understood project.
James On Sat, Jan 8, 2011 at 8:53 AM, Yuri Z. (a.k.a Vega) <[email protected]>wrote: > I think it would be nice to make the Java (Derby) as default DB. That > would reduce minimal requirements to run Wiab. > > On Jan 7, 5:42 pm, Asif Khan Gillani <[email protected]> wrote: > > I think this kind of solution will be easier to understand, document > > and maintain. We can easily implement JPA without making entities for > > everything. We just have to create entities to hold file content for > > each kind of store. > > Kindly guide me if there is any technical thing in adopting the > > current file based mechanism for storage in DBs. > > > > On Jan 7, 7:49 pm, John Blossom <[email protected]> wrote: > > > > > > > > > > > > > > > > > It certainly would make sense. The LAMP stack will be there by default, > and > > > if people want to use another SQL-serving mechanism they may. Hopefully > this > > > would help to manage these state issues more flexibly, otherwise > there's the > > > probability that the "simple" file solution becomes a bespoke database > > > solution that will be very troublesome to maintain. > > -- > 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.
