Bei MCast gibt es ja eben genau keinen Buffer.
Halte ich ja mal für ein ziemliches Gerücht.
http://www.juniper.net/techpubs/en_US/junos10.4/topics/concept/multicast-uses.html
With unicast traffic, many streams of IP packets that travel across networks flow from a single source, such as a Web site server, to a single destination such as a client PC. This is still the most common form of information transfer on networks.
Broadcast traffic flows from a single source to all possible destinations reachable on the network, which is usually a LAN. Broadcasting is the easiest way to make sure traffic reaches its destinations.
Television networks use broadcasting to distribute video and audio. Even if the television network is a cable television (CATV) system, the source signal reaches all possible destinations, which is the main reason that some channels' content is scrambled. Broadcasting is not feasible on the public Internet because of the enormous amount of unnecessary information that would constantly arrive at each end user's device, the complexities and impact of scrambling, and related privacy issues.
Multicast traffic lies between the extremes of unicast (one source, one destination) and broadcast (one source, all destinations). Multicast is a “one source, many destinations” method of traffic distribution, meaning only the destinations that explicitly indicate their need to receive the information from a particular source receive the traffic stream.
On an IP network, because destinations (clients) do not often communicate directly with sources (servers), the routers between source and destination must be able to determine the topology of the network from the unicast or multicast perspective to avoid routing traffic haphazardly. Multicast routers replicate packets received on one input interface and send the copies out on multiple output interfaces.
In IP multicast, the source and destination are almost always hosts and not routers. Multicast routers distribute the multicast traffic across the network from source to destinations. The multicast router must find multicast sources on the network, send out copies of packets on several interfaces, prevent routing loops, connect interested destinations with the proper source, and keep the flow of unwanted packets to a minimum. Standard multicast routing protocols provide most of these capabilities, but some router architectures cannot send multiple copies of packets and so do not support multicasting directly.
http://forum.golem.de/kommentare/in...t-vs.-unicast/72136,3311194,3311194,read.html
http://www.haveyouherd.com/pg43.cfm
http://security.americandynamics.ne...mission-vs-Unicast-video-transmission-methods
http://forums.anandtech.com/showthread.php?t=1277407
Und da sind wir wieder, da W-LAN Hardware halb duplex ist und sich nicht wesentlich anders verhält wie ein Hub, würde ich von Multicast mal die Finger lassen.
Zu mal ich den Sinn von mehrern Listeners bei FPV nicht sehe.
Halte ich ja mal für ein ziemliches Gerücht.
http://www.juniper.net/techpubs/en_US/junos10.4/topics/concept/multicast-uses.html
With unicast traffic, many streams of IP packets that travel across networks flow from a single source, such as a Web site server, to a single destination such as a client PC. This is still the most common form of information transfer on networks.
Broadcast traffic flows from a single source to all possible destinations reachable on the network, which is usually a LAN. Broadcasting is the easiest way to make sure traffic reaches its destinations.
Television networks use broadcasting to distribute video and audio. Even if the television network is a cable television (CATV) system, the source signal reaches all possible destinations, which is the main reason that some channels' content is scrambled. Broadcasting is not feasible on the public Internet because of the enormous amount of unnecessary information that would constantly arrive at each end user's device, the complexities and impact of scrambling, and related privacy issues.
Multicast traffic lies between the extremes of unicast (one source, one destination) and broadcast (one source, all destinations). Multicast is a “one source, many destinations” method of traffic distribution, meaning only the destinations that explicitly indicate their need to receive the information from a particular source receive the traffic stream.
On an IP network, because destinations (clients) do not often communicate directly with sources (servers), the routers between source and destination must be able to determine the topology of the network from the unicast or multicast perspective to avoid routing traffic haphazardly. Multicast routers replicate packets received on one input interface and send the copies out on multiple output interfaces.
In IP multicast, the source and destination are almost always hosts and not routers. Multicast routers distribute the multicast traffic across the network from source to destinations. The multicast router must find multicast sources on the network, send out copies of packets on several interfaces, prevent routing loops, connect interested destinations with the proper source, and keep the flow of unwanted packets to a minimum. Standard multicast routing protocols provide most of these capabilities, but some router architectures cannot send multiple copies of packets and so do not support multicasting directly.
http://forum.golem.de/kommentare/in...t-vs.-unicast/72136,3311194,3311194,read.html
http://www.haveyouherd.com/pg43.cfm
http://security.americandynamics.ne...mission-vs-Unicast-video-transmission-methods
http://forums.anandtech.com/showthread.php?t=1277407
Und da sind wir wieder, da W-LAN Hardware halb duplex ist und sich nicht wesentlich anders verhält wie ein Hub, würde ich von Multicast mal die Finger lassen.
Zu mal ich den Sinn von mehrern Listeners bei FPV nicht sehe.
Zuletzt bearbeitet: