On Sat, May 15, 2021 at 10:52 AM Alexander <[email protected]> wrote:
Thanks for these comments. Because it was documented as not being part of core and I was not > familiarized with the code of recent years, I was also initially confused > by this file[1], residing in /external/leoserver/ -- an older development, > which is a web (http) server. > leo/external/leoserver.py no longer exists. This leoserver.py is a web socket server[2] (probably should have been > explicit in the doc from the start), and is located in /core/ despite not > being part of core, and isn't yet part of devel. > I've just added the word "socket" to the first sentence of the chapter. > New implementations through this server are going to be interesting > projects. > Yes. One could imagine *additions* to the server that communicate with vim, or other editors or IDE's. > For now, I suppose the key to understanding the payloads will be > leoserver.py, leoclient.py[3], and currently implemented leoInteg[4]. > Exactly. Except for the main loop (ws_handler), the code is surprisingly easy. Incoming requests get dispatched to straightforward handlers. 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS0cMx4h_XN9os1yS-Hn4rTh%3DUhypmh8OsWP1PaJXa4Tig%40mail.gmail.com.
