On Tue, 30 Oct 2018 11:50:12 -0500 "Edward K. Ream" <edream...@gmail.com> wrote:
> On Tue, Oct 30, 2018 at 11:07 AM Terry Brown <terrynbr...@gmail.com> > wrote: > > I do wonder if it's necessary to include development of a websockets > > layer in LeoWapp. Maintenance burden, complexity, all that. > > > > Flexx is a Python framework that uses websockets, there are probably > > others. > > > > Also there a lots of web app. frameworks (Flask, Django, etc.) which > > don't use websockets by default (they use regular AJAX), but can. > > That welcome news. I agree we should use the highest level tools > available. > > I'll study Flexx, Flask and Django next. I had no idea they could use > websockets. > > What framework do you prefer? They're all very different. I've used Django quite a bit in the past, and would again for large web based applications. It handles user logins, rights management, templates, database binding and updating, form generation, etc. etc. Probably not the right weight for LeoWapp. I don't know what it's like for web-sockets, "Django Channels" use web-sockets, that's all I know. Haven't used Flask, just fiddled with tutorial. No idea if its websocket support is very mature / well integrated. Am playing with Flexx experimenting with visualizing multiple graphs, thought I'd mentioned that although not seeing the post now. Flexx uses web-sockets by default / exclusively, so it's probably going to be the most solid there. Flexx's approach is idiosyncratic enough that you're probably stuck with it if you use it (it translates Python to Javascript :-) but there might be options which let you separate the transport layer. Certainly this would be the case if you were using regular AJAX, I'm less familiar with options for websockets. I'm thinking the decision that LeoWapp will use websockets is fine, but you won't always see the performance benefits of websockets over AJAX. On a local machine AJAX should be fast enough, seeing the "network" is basically in memory, and over remote links I suspect (not sure) that you'll need good low latency connectivity or the network will be the bottleneck, not the transport protocol. Don't want to dissuade you from websockets, just that AJAX is more common and therefore easier for Google to answer random questions etc. etc. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
