User’s demands have changed and our requirements of the web have grown. These changes make HTTP a major bottleneck. The HTTP standard itself and TCP are both huge issues. Large data centers moving copious amounts of data from one end-point to the other have latency and cost issues associated with outdated Internet architecture. HTTP is especially problematic when users are experiencing low throughput, limited bandwidth, degraded network connectivity, or requiring a near real-time response. The first step in the construction of the Universal Web is to replace HTTP and TCP entirely with UDSP.

If a developer was to imagine how UDSP works think of UDSP as a mixture of QUIC and Web Sockets. Like websockets UDSP opens a stream between a client and a server and it says open for the life cycle of the application or until it's no longer needed. A user can browse a website while downloading a large file from it all over the same UDSP connection. Multiple assets over time can be requested from the service which can stream over and assemble the full data on the client side. All while the server can push updates to the client and the client can push updates to the server all over the same UDSP connection.

UDSP is great for machine-to-machine communication and the world of IoT. The packets are specifically designed to be easily digested and quickly utilized. UDSP is for low-latency high-throughput communication making it ideal for dispersed computing and parallel computing environments which require dynamic changes to the protocol.