ated read operations
        can cause socket writes. However, these writes will not compete with caller-initiated
        write operations. For the purposes of correctness with respect to the stream
        invariants, caller-initiated read operations still only count as a read.
        This means that callers can have a simultaneously active read, write, and
        ping/pong operation in progress, while the implementation also automatically
        handles control frames.
      </p>
<h5>
<a name="beast.u