It has been noticed that there is a perceived delay in response from the Lightweight HTTP Server implementation that ships with the JDK, compared to other production HTTP Servers. The cause for this delay has been identified as the Nagle algorithm buffering the response data until there is sufficient data ( not always the case especially for headers ), or a timeout occurs that triggers the data to be sent.
This CR is requesting that a property be provided to allow applications to effectively set the TCP_NODELAY socket option on sockets being used by the server, i.e. disable Nagle. This is similar to what other production HTTP servers provide. For example, see: