I'm not necessarily saying that it doesn't do what it's supposed to. I'm saying that the draft doc doesn't say what it is supposed to do, at least not so an inexperienced user can do anything with it. I'm saying that this draft doc doesn't tell the reader what and how it's doing those things. OK, it says to run it with parameters. But it doesn't say how to compose a message nor how to receive one, nor which of those **_do_message things are supported. The other things I wrote were in the way of suggestions of features or behavior of the server.
Viktor wrote that the server isn't really intended to be an HTTP server at all. Now that I've skimmed the Web Sockets RFC, I see a little better what's going on with respect to the "web server-ness" of the server. So let's have the doc say that it is a WS server per the RFC, and explain more about the messages so I would be able to actually construct, send, and reply to one. On Saturday, May 15, 2021 at 6:12:42 AM UTC-4 Edward K. Ream wrote: > On Fri, May 14, 2021 at 11:39 PM [email protected] <[email protected]> > wrote: > >> Looking at this and thinking about it a bit for the first time, I have >> the reaction that an HTTP server should respond to at least GET and POST >> requests. > > > Why do you say that? leoserver.py does what it is supposed to do. > > Edward > ----------------------------------------------------------------- > Edward K. Ream: [email protected] > An old man, crazy about computer programming. > Leo Editor: http://leoeditor.com/ > ----------------------------------------------------------------- > -- 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/aca39915-2dd9-4ed1-81c5-578bb9cf7974n%40googlegroups.com.
