On Wed, Mar 20, 2013 at 7:59 PM, David McNab > I'm writing now to ask what the thinking is regarding getting a > cloud-ready version of Leo up and running. > > I'm thinking about various usage patterns, such as: > [Snip] I'm of the strong opinion that, whichever way Leo goes, it needs to move away from the XML .leo file as its principal storage format, and move towards database storage, with a one-node-per-db-record mapping and support for automatic acquisition/release of node locks. IMHO, the.leo file should be put out to pasture and work just as a very handy import/export format. It's still a great way to pack a whole heap of (non-thin) files together with coherent structure.
> > Thoughts? > My first thought: it would be great it you could join us in Duluth for the Leo sprint :-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
