From: jj4public@gmail.com   
      
   On Sun, 17 Oct 2021 15:03:37 -0700 (PDT), muta...@gmail.com wrote:   
   > On Sunday, October 17, 2021 at 6:40:56 PM UTC+11, JJ wrote:   
   >   
   >> Use the appropriate HTTP request header to keep the connection open.   
   >> However, the HTTP server must also support the header.   
   >   
   > I'm confused by this. It seems to be the browser that is   
   > initiating a new request instead of reusing the current   
   > connection. Maybe that's a Javascript limitation?   
   >   
   > Regardless, I tried sending this:   
   >   
   > #define KEEP_ALIVE "HTTP/1.1 200 OK\r\n" \   
   >               "Connection: Keep-Alive\r\n" \   
   >               "\r\n"   
   >   
   > before the HTML page, but it didn't change the behavior.   
      
   Which is why the header must be supported by the server too. Not just the   
   client. And actually do something as requested, rather than "just talks".   
      
   >> Though IMO, it's better to use WebSocket for this kind of purpose.   
   >   
   > Note that the goal is for the server to be very simple, rendering   
   > an HTML page instead of an ANSI terminal. Just a whole lot of   
   > lines with 
 between them. And the terminal will be simple   
   > too, just assuming the javascript is correct, not bothering to   
   > parse it. My understanding is that websockets are a more   
   > complicated thing.   
   >   
   > And note that going across the internet, I'm just going to have   
   > the serial ports on both ends using an emulator to talk TCP/IP.   
   > In a business setting there could potentially be a real serial   
   > cable.   
   >   
   > BFN. Paul.   
      
   WebSocket guarantees that the network connection is reused. But neither one   
   matter if the server doesn't do anything to keep the connection alive.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)