Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
My manager has asked me to assess what changes would be required to add multicast support to a socket-based TCP/IP networking program that is part of a trading system.
As far as I can tell, from the perspective of a Java program, it doesn’t seem to matter too much whether the program is unicast or multicast.
Doesn’t the Java networking API make all of this transparent? By this I mean, wouldn’t the change be a simple one of simply adding additional destinations for the outgoing connections?
As far as I know, TCP doesn’t have support for multicast. Multicast is often done via UDP. UDP by design is not a reliable transport. I-e there is no guarantee of datagram reaching its destination and there is no delivery report when it does reach the destination.
Some reliable multicast solutions are discussed in this question but they are in-essence different protocols.
So if you your application needs to guarantee delivery while using multicast, you will certainly need do some changes in your communication layer.