On Mon, Apr 1, 2013 at 7:41 AM, Seth Johnson <[email protected]> wrote: > And your document could have nodes that link to documents on other Leo > servers, providing the same API.
The choice of a massively scalable backend would assure the participants in the Leo network would be able to support huge contexts, like everybody in the world could have accounts or store data on your endpoint if you wanted to do it that way, or you could make spiders that gathered data from the entire web, or the entire potential Leo web. Seth > On Mon, Apr 1, 2013 at 3:52 AM, Ville M. Vainio <[email protected]> wrote: >> I would do it by creating a web server that serves a leo document over >> RESTful api, then integrate support for this service in Leo (where "save" >> would send changes, etc) >> >> It could use a db, flat file system or live leo process as backing store. >> This is a minor implementation detail. >> >> >> On Mon, Apr 1, 2013 at 5:45 AM, Seth Johnson <[email protected]> >> wrote: >>> >>> On Sun, Mar 31, 2013 at 12:10 PM, Ville M. Vainio <[email protected]> >>> wrote: >>> > If Leo supported lazy loading of nodes, db would allow huge docs w/ >>> > small >>> > ram footprint & load times. >>> > >>> > As for networked access, db seems like wrong way to do it (dB's don't >>> > work >>> > well over internet) >>> >>> >>> Curious how else you'd do it. Interface with documents on a web site? >>> Build it on a P2P sort of platform layer (that might be built on a db >>> or documents at the nodes, in fact)? The interesting thing to me >>> would be massively scalable and distributed Leo on a NoSQL backend. >>> >>> >>> Seth >>> >>> >>> > On Mar 31, 2013 6:28 AM, "Terry Brown" <[email protected]> wrote: >>> >> >>> >> On Sat, 30 Mar 2013 14:56:55 -0700 (PDT) >>> >> "Edward K. Ream" <[email protected]> wrote: >>> >> >>> >> > So let's refocus on the future of Leo. What problems with Leo (or >>> >> > .leo >>> >> > files) would DB's be likely to solve? This would be a good topic to >>> >> > discuss at the sprint. Your comments, please. >>> >> >>> >> That was why I said you'd have to stop thinking about Leo if you wanted >>> >> to learn about the functionality of DBs, which is no compulsory :-) >>> >> >>> >> Leo's data storage needs are very simple, a list of nodes, a list of >>> >> edges. DBs are one very easy way to get networked storage, and they >>> >> also offer opportunities for versioning. git is another networked out >>> >> of the box data store that might work. I think DB's relevance to Leo >>> >> are networking and versioning, not table relating and querying. >>> >> >>> >> I don't think this line of thought is about fixing Leo - it's ability >>> >> to load and save data locally's fine, apart from multi-outline save >>> >> speed, and that's not a huge issue. So this is about new capabilities, >>> >> networked, possibly collaborative data, etc. >>> >> >>> >> If we want things to fix, we can look at the list SegundoBob's >>> >> generating :-} >>> >> >>> >> Cheers -Terry >>> >> >>> >> -- >>> >> 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. >>> >> >>> >> >>> > -- >>> > 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. >>> > >>> > >>> >>> -- >>> 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. >>> >>> >> >> -- >> 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. >> >> -- 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.
