The main advantage of Ghost Multicasting is that the downloading time is extremely shortened as only one PC is downloading the image off the Server which dramatically reduces the risk of heavy network traffic. The only disadvantage is that the PC chosen to be the Ghost Server has to have enough free hard drive space to store the image which will then be redistributed. Manually Specified Ghost Multicast? Using this method you have to manually assign unique IP addresses for the Client PCs by using and configuring the wattcp.
This is useful when you're doing an expensive operation like a network request. You don't want to repeatedly execute identical network requests for each subscriber - you just want to execute one then multicast the results.
There are two ways to multicast: Use a ConnectableObservable via publish or replay 1 Use a Subject Any work done before the ConnectableObservable or Subject will only happen once, then that work will be multicast to all downstream Subscribers.
There is a subtle point here you must recognize: Streams only multicast at the point of the ConnectableObservable or Subject. As a result, any work done after the multicast is duplicated per Subscriber.
Let's look at an example of how this can come into play: Event Here we have a ConnectableObservable, an expensive map operation and two Subscribers. The surprising result is that the expensive map operation is executed twice, even though we tried to prevent that with publish!
This chart makes the situation clearer: If you actually wanted the map to happen once, you would need to put it before the publish call: Event Here's an updated chart: What's the lesson here?
If you're relying on multicasting to reduce work, make sure you multicast at the right point. For better or worse, a lot of people are using Subjects. One advantage is that they are multicast but you have to remember that they are only multicast at the point they emit. If you have a bunch of expensive operators applied downstream of the Subject then you should consider adding another publish somewhere downstream.The multicasting package loads an image file captured from a ‘source’, onto a number of ‘client’ computers simultaneously.
However, you need a dedicated Ghost Multicast Server machine to control the session. Multicasting sessions can be scheduled to run at specified times or after a certain number of clients join a session. Ghost Multicasting - Ghost Multicasting allows one computer, the Ghost Server, to download a Ghost image from the Server and then redirects the image to other workstations, the Ghost Clients, through the use of TCP/IP settings over the network.
I had a customer complaining about intermittent connection drops, high latency and general problems with his Skype and online gaming.
I discovered Multicast was enabled on his radio as well as the AP he was connected to and other clients on the AP. Ghost Multicasting. The Two Methods Of Ghost Multicasting. Manually Specified Ghost Multicast C Losing this method you have to manually assign unique IP addresses for the Client PC’s by using and configuring the watch.
Enabling basic multicast routing functionality on your network does not require a lot of work and can be implemented fairly quickly.
Some configuration is done in Global Configuration mode and some configuration is done in Interface Configuration mode.
Enabling multicast routing The first command that you perform in Global Configuration mode is the ip multicast-routing [ ]. How Ghost Multicasting communicates over the network Question/Issue: X Search Advanced Search Options This document discusses how Ghost performs multicasting for sending an image from the server to the client.
Other Support Resources l Support Forums Ask an expert.