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]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
