"Edward K. Ream" <[email protected] <javascript:>> wrote:
> > We can start by assuming ajax > > <https://www.w3schools.com/xml/ajax_xmlhttprequest_create.asp>, using > > http. > > Sounds a good way of communicating :-) Terry wrote: > I wonder if Cormac was thinking of frameworks like Django, but perhaps > more appropriate (lighter) for Leo, Flask? > > Cheers -Terry > I was concentrating less on the actual technology to be used, but rather on the questions that I would ask before you start talking about the technology. For example, I'm sure there are people out there serving leo files from FTP, cloud disks etc. Whilst technically that is client / server, effectively there is little additional benefit from doing so apart from files available at a distance. On the other hand, there is the example of a web app like google docs spreadsheet, where multiple people can work on the sheet at the same time, it an be scaled to arbitrary sizes in terms of data and load etc. Code can be written to run server side as well as client side. This thread was posted at the same time as I was exploring the leo code looking to answer the question :- "What is the smallest amount of changes necessary so as to read and write outlines from an ArangoDB database" :-) Regards, Cormac. -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
