This is the case for most of the web applications.

Many, many users, but your server is waiting 🕙 for their not-so-good connection to send their requests.

And then waiting 🕙 again for the responses to come back.

This "waiting" 🕙 is measured in microseconds, but still, summing it all, it's a lot of waiting in the end.

That's why it makes a lot of sense to use asynchronous ⏸🔀⏯ code for web APIs.

		r, w := io.Pipe()
		// Make sure we close the pipe so blocked writes doesn't stay around.
		defer r.CloseWithError(context.Canceled)

		readers[i] = newMetacacheReader(r)
		d := disks[i]

		// Send request to each disk.
		go func() {
			var werr error
			if d == nil {
				werr = errDiskNotFound
			} else {
				werr = d.WalkDir(ctx, WalkDirOptions{
					Limit:          opts.perDiskLimit,

    public void startDocument() throws SAXException {
        tagQueue = new LinkedList<>();
        labelList = new ArrayList<>();
        labelType = null;
    }

    /**
     * SAX event handler called at the end of document parsing.
     * Cleans up internal data structures used during parsing.
     *
     * @throws SAXException if a SAX error occurs during cleanup
     */
    @Override

		t.Fatalf("scan failed: %v", scanner.Err())
	}
	if token := scanner.Text(); token != word {
		t.Fatalf("unexpected token: %v", token)
	}
}

// Test that empty tokens, including at end of line or end of file, are found by the scanner.
// Issue 8672: Could miss final empty token.

func commaSplit(data []byte, atEOF bool) (advance int, token []byte, err error) {
	for i := 0; i < len(data); i++ {

    /**
     * Named pipe status indicating the connection is established and operational.
     */
    public static final int STATUS_CONNECTION_OK = 3;

    /**
     * Named pipe status indicating the server end of the pipe is closed.
     */
    public static final int STATUS_SERVER_END_CLOSED = 4;

    private int available;

    /**
     * Constructs a TransPeekNamedPipeResponse with the specified configuration.
     *

 *
 * @author mbechler
 */
public interface FileInformation extends Decodable, Encodable {

    // information levels

    /**
     * File end-of-file information class constant.
     */
    byte FILE_ENDOFFILE_INFO = 20;

    /**
     * File basic information class constant.
     */
    byte FILE_BASIC_INFO = 0x4;
    /**

    return readUnsignedByte() != 0;
  }

  /**
   * Reads a byte from the input stream checking that the end of file (EOF) has not been
   * encountered.
   *
   * @return byte read from input
   * @throws IOException if an error is encountered while reading
   * @throws EOFException if the end of file (EOF) is encountered.
   */
  private byte readAndCheckByte() throws IOException, EOFException {

    }

    @Test
    @DisplayName("Should handle null in middle of multiple elements")
    void testJoinNullInMiddle() {
        String result = StringUtil.join("-", "start", null, null, "end");
        assertEquals("start-null-null-end", result);
    }

	dst := src[:0]
	for _, s := range src {
		pos, end := s.Offset, s.endOffset()
		pos += blockPadding(+pos) // Round-up to nearest blockSize
		if end != size {
			end -= blockPadding(-end) // Round-down to nearest blockSize
		}
		if pos < end {
			dst = append(dst, sparseEntry{Offset: pos, Length: end - pos})
		}
	}
	return dst
}

The application would process the request and send a **plain (unencrypted) HTTP response** to the TLS Termination Proxy.

<img src="/img/deployment/https/https06.drawio.svg">

### HTTPS Response { #https-response }

The TLS Termination Proxy would then **encrypt the response** using the cryptography agreed before (that started with the certificate for `someapp.example.com`), and send it back to the browser.