Detecting EOF / TCP teardown using Java sockets from Javascript

Question

I'm creating a Java socket in Javascript, sending an HTTP request and receiving a response correctly but I seem to be unable to detect an EOF or the server closing the socket at the end. What am I doing wrong? The problem is we never exit the outermost while loop - the server stops transmitting and (presumably) closes its end of the connection, yet receiver.read() never returns -1 and all the socket methods return state consistent with the socket still being connected.

    var s = new java.net.Socket("www.google.com",80);
    var sender = new java.io.PrintStream(s.getOutputStream());
    var receiver = s.getInputStream();
    sender.print("GET / HTTP/1.0\r\n\r\n");
    sender.flush();
    s.shutdownOutput();
    var response = '';
    var eof = 0;
    while( !eof && s.isConnected() && s.isBound() && !s.isClosed() && !s.isInputShutdown() )
    {  
       if( receiver.available() )
       {
        while( receiver.available() )
        {
         var i = receiver.read();
         if( i == -1 ) { eof = 1; }
         else { response += String.fromCharCode(i); }
        }
        // at this point response does contain the expected HTTP response
       }
    }

    // in case remote end closed the socket before we got a chance to read all the bytes from it        
    // ...but this is never reached!
    while( receiver.available() )
    { 
      response += String.fromCharCode(receiver.read());
    }

    alert( response );

Answer 1

Ok. What's the value of eof when the code reaches this comment?
// at this point response does contain the expected HTTP response

What's the symptom? I assume it's an infinite loop?

Answer 2

OK, further research suggests there is no non-blocking way to discover whether the remote side has closed a socket. However, it is possible to achieve this using NIO channels:

    var s = new java.nio.channels.SocketChannel.open(new java.net.InetSocketAddress( "www.google.com",80) );
    //ew, but while we're prototyping...
    s.configureBlocking(true); 
    var sender = new java.io.PrintStream(s.socket().getOutputStream());
    sender.print("GET / HTTP/1.0\r\n\r\n");
    sender.flush();

    s.configureBlocking(false); // yayy!

    var response = '';
    var len = 0;
    var dbuf = java.nio.ByteBuffer.allocate( 1024 );
    while( len >= 0 )
    {    
         len = s.read( dbuf );
         dbuf.flip();
         while( dbuf.hasRemaining() )
         { 
           response += String.fromCharCode( dbuf.get() );
         }
         dbuf.clear();
    }

    alert( response );

Answer 3

When the end of the stream is reached, available() returns 0, so in your code, you never read the -1