[email protected] schrieb am Samstag, 15. Mai 2021 um 06:39:53 UTC+2: > 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. The draft docs say nothing about this. The server docs should > at least explain how to send a request to the server. It should not be left > to the sample client. And if there is to be a web server, it would be > useful for it to serve one or a few actual web pages, which could in fact > contain the documentation for using it. Tomcat does this by default, for > example. > > As an example of what I mean, the draft doc says > > "The **_do_message** method expects that incoming requests are JSON object > ..." >
After reading the source a bit, it became clear to me, that it's not intended to offer an HTTP(s) [1] interface, but its providing a WS(S) [2] interface. If I understand it correctly, this is at a much lower / generic level. With kind regards, Viktor --- [1] https://datatracker.ietf.org/doc/html/rfc7231 [2] https://datatracker.ietf.org/doc/html/rfc6455 -- 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/3bf1e072-9872-48b2-9925-62f5f65d455an%40googlegroups.com.
