<p> A {@link Stream} represents a bidirectional exchange of data on top of a {@link Session}. </p> <p> Differently from socket streams, where the input and output streams are permanently associated with the socket (and hence with the connection that the socket represents), there can be multiple HTTP/2 streams present concurrent for a HTTP/2 session. </p> <p> A {@link Stream} maps to a HTTP request/response cycle, and after the request/response cycle is completed, the stream is closed and removed from the session. </p> <p> Like {@link Session}, {@link Stream} is the active part and by calling its API applications can generate events on the stream; conversely, {@link Stream.Listener} is the passive part, and its callbacks are invoked when events happen on the stream. </p>