How is bursting different from HTTP streaming?
The principle differences between Bursting and HTTP Streaming are as follows: 1) Bursting is network centric, HTTP streaming is client-centric. This means that, in the HTTP streaming scenario, there is no tracking of bandwidth, and no optimization of network resources, resulting in higher costs. 2) Streamed multimedia is greed-based instead of need-based – multimedia is streamed first-come-first-served to the client with the biggest pipe and the fastest processor, rather than burst on an as-needed basis to keep client buffers filled. 3) Burstware®’s Optimized Connection Acceptance Criteria ensures high quality for everyone. Streaming has no such criteria applied. Less fortunate viewers are data-starved, which diminishes their viewing and listening experience. 4) Burstware® employs a failover scheme. There is no such feature in HTTP streaming. 5) Burstware® handles files of all sizes, including very large files. Streaming is designed to handle fairly small files. Because of these differ
