http_server: WebSocket server to set flag in transmitted messages by default

Add logic to set `FIN` flag automatically for transmitted WS frames, but
if `fragmented` option set indicating an expert/manual mode, then the
`FIN` flag is set according to the `final` option.

examples/protocols/http_server/ws_echo_server/README.md

@@ -10,7 +10,12 @@ ws_server_example_test.py could be used as a simple WS client).
 
 The server registers WebSocket handler which echoes back the received WebSocket frame. It also demonstrates
 use of asynchronous send, which is triggered on reception of a certain message.
-Please note that the WebSocket HTTPD server does not automatically fragment messages, so the application code must deal with fragmentation, setting `final` flag as appropriate. Single (complete/unfragmented) WebSocket frames must have the `FIN` flag set to be accepted as valid  (see [RFC6455, section 5.4](https://tools.ietf.org/html/rfc6455#section-5.4)).
+
+Please note that the WebSocket HTTP server does not automatically fragment messages.
+Each outgoing frame has the FIN flag set by default.
+In case an application wants to send fragmented data, it must be done manually by setting the
+`fragmented` option and using the `final` flag as described in [RFC6455, section 5.4](https://tools.ietf.org/html/rfc6455#section-5.4).
+
 
 ### Hardware Required
 

examples/protocols/http_server/ws_echo_server/main/ws_echo_server.c

@@ -48,7 +48,6 @@ static void ws_async_send(void *arg)
     ws_pkt.payload = (uint8_t*)data;
     ws_pkt.len = strlen(data);
     ws_pkt.type = HTTPD_WS_TYPE_TEXT;
-    ws_pkt.final = true;
 
     httpd_ws_send_frame_async(hd, fd, &ws_pkt);
     free(resp_arg);