certainly, sql persistence would be a great leap forward, but, since MySQL became Oracle's(with all respect, I think there MAY be problems with its free license or proper development) and here were some interesting attempts with MongoDB(modern way) i think its much more appropriate to choose by default PostgreSQL (so many projects choose it now) or , at least - MariaDB
I don't think there would be problems with finding PostgreSQL hosting for people that want to implement WIAB , since - more or less it still would be pretty heavy project, not situated for simple site needs with simple hosting plans but for VPS / VDS or so, were isn't complications to install any DB so please, at least - make support for Postgres too, as , like you could see for now - it is, at least - very popular choice DB for serious but OpSo projects, and integrating with existing DB would be much easier for many. On Jan 7, 4: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]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
