So the way it works for typical web interfaces is that on the client side you will use an HTML video or audio element. Those already have the streaming capability built in. It is not really a stream though, because it is still HTTP based. Instead it is a regular old HTTP 1.1 GET request with a range header.

The web server sees the range header and then responds with a small slice of the media and a HTTP 206 response. That's really all there is to it from a regular web implementation.

You could also play around with proper streams. This would work by creating a file system stream and piping the output to a network socket. This is really just as simple as it sounds, but you will have to make some decisions on network protocol and remote interface.