As it is implemented now, by default dstp transfers the most recent data on the server to the subscribers of the measurement data. In other words, subscribers are not guaranteed to receive every instance of data that gets published on the server. If the publisher is writing data to the server at a faster rate than the server is sending data to its subscribers, the subscribers might not get previously published data. This might seem to be a shortcoming of dstp; however, the most recent value of the measurement data is usually of the most interest for most measurement applications. The working principle is exactly the same as a digital voltmeter (DVM). The DVM displays the value of the voltage difference between two points at that instant. By transmitting the most recent data, you can use dstp in high-performance measurement applications. However, data loss can minimized or even eliminated by buffering data at the client and/or the server. dstp now offers both client-side and server-side data buffering. Client-side buffering can be configured through URL options, while server-side buffering can be configured through the DataSocket Server Diagnostic dialog box in the server.