• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

Card Range To Study

through

image

Play button

image

Play button

image

Progress

1/11

Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

11 Cards in this Set

  • Front
  • Back

True or False: A reason to use HTTP as the deliver protocol for streaming services is - HTTP streaming isn't spreading widely as a form of delivery ofInternet video.

False -HTTP streaming is spreading widely as a form of delivery ofInternet video.

True or False: A reason to use HTTP as the deliver protocol for streaming services is - There is a clear trend towards using HTTP as the main protocolfor multimedia delivery over the Open Internet.

True

True or False: A reason to use HTTP as the deliver protocol for streaming services is - HTTP-based delivery enables easy and effortless streamingservices by avoiding NAT and firewall traversal issues.

True

True or False: A reason to use HTTP as the deliver protocol for streaming services is - HTTP-based delivery provides reliability and deploymentsimplicity due as HTTP and the underlying TCP/IP protocolare not widely implemented and deployed.

False - HTTP-based delivery provides reliability and deploymentsimplicity due as HTTP and the underlying TCP/IP protocolare widely implemented and deployed.

True or False: A reason to use HTTP as the deliver protocol for streaming services is - HTTP-based delivery provides the ability to use standardHTTP servers and standard HTTP caches (or cheap servers ingeneral) to deliver the content, so that it can't be deliveredfrom a CDN or any other standard server farm.

False - HTTP-based delivery provides the ability to use standardHTTP servers and standard HTTP caches (or cheap servers ingeneral) to deliver the content, so that it can be deliveredfrom a CDN or any other standard server farm.

True or False: A reason to use HTTP as the deliver protocol for streaming services is - HTTP-based delivery provides the ability to move control of“streaming session” entirely to the client. The client basicallyonly opens one or several or many TCP connections to one orseveral standard HTTP servers or caches.

True

True or False: A reason to use HTTP as the deliver protocol for streaming services is - HTTP-based delivery provides the ability to the client toautomatically choose initial content rate to match initialavailable bandwidth without requiring the negotiation withthe streaming server

True

True or False: A reason to use HTTP as the deliver protocol for streaming services is - HTTP-based delivery provides a simple means to seamlesslychange content rate on-the-fly in reaction to changes in availablebandwidth, within a given content or service, with requiring negotiation with the streaming server

False - HTTP-based delivery provides a simple means to seamlesslychange content rate on-the-fly in reaction to changes in availablebandwidth, within a given content or service, withoutrequiring negotiation with the streaming server

True or False: A reason to use HTTP as the deliver protocol for streaming services is - HTTP-based streaming has the potential to accelerate fixedmobileconvergence of video streaming services as HTTP basedCDN can't be used as a common delivery platform.

False - HTTP-based streaming has the potential to accelerate fixedmobileconvergence of video streaming services as HTTPbasedCDN can be used as a common delivery platform.

What was DASH designed for?

1)to support delivery of media components encapsulated inISO base media file format box structure


2) to address delivery whereas presentation, annotation and userinteraction is largely out-of-scope


3) to permit integration in different presentation frameworks.

What are three features DASH supports?

fast initial startup and seeking,• bandwidth-efficiency,• adaptive bitrate switching,• adaptation to CDN properties,• re-use of HTTP-server and caches,• re-use of existing media playout engines,• support for on-demand, live and time-shift delivery services,• simplicity for broad adoption.