You are not logged in.
I know that a data stream is a big chunk of data, like a pipeline with two end points wherein data is put in one end and comes out the other.
Now, over the internet if a client machine requests for a file located on a server (according to what I know), the file is broken down into small packets wherein each packet has the source address and the destination address and it is sent to the respected destination and it can take any path over the network to reach to its destination.
If streaming works like the way i think it is i.e., like a pipeline with two end points where data is put in one end and comes out the other then does the end point from where the data is put in contains the source address and the end point from where the data has to come out contains the destination address.
Does it create a virtual pipe from source to the destination over the internet ? if it creates a virtual pipeline then what would happen if at some location over the path a network outage occurs ? won't all the streams of data will be lost ? how does it handles a situation like this ?
Well, exact behaviors depend a lot on just what protocols you're talking about being used for the transfer... If you're talking about something running on top of TCP, then that has lots of error recovery behavior built in, and it'll take care of resending seemingly lost packets and such to try to recover from temporary network problems... But, if the network outage is serious and long-lasting enough, then eventually even it will give up... The sending and receiving apps should both be able to notice the failure if they're paying attention, so they could handle it however makes sense for what they're doing (eg: the sender can try resending again later, and the receiver can either throw away the partial file or keep what it's got and tell the sender to pick up where it left off last time)...