Users of real-time audio/visual data can tolerate some loss, as long as it isn’t
too noticable, whereas users of data transfers such as financial transactions,
database records and so on cannot. Clicks or gaps in the audio can be ignored,
and some video frames, or parts of video frames, can be lost without the viewer
really noticing, but for normal data, errors or loss can be catastrophic, particularly
if the errors are initially undetected. At first sight this might seem to be
an advantage of multimedia data over error-sensitive data. Unfortunately, most
protocols (such as TCP/IP) are designed for error-sensitive data, and if a part
of a message is lost, they will invoke mechanisms for recovering the lost data,
usually through re-transmissions. This is exactly what is NOT wanted for real-time
mulltimedia, since the re-transmissions introduce additional delay and jitter
into the video stream so that not only does the re-transmitted data arrive too
late to be useable, it also occupies vital bandwidth unnecessarily.
In summary, the characteristics of multimedia transmissions over a network are
quite different to those of non real-time, error-sensitive data, and introduce
a whole new set of challenges for server, network and client design.