Different ways in which clients and servers can communicate??
One of the way is through sockets.
I wanted to explore additional options...
Stacey Warren - Expert brainly.com
Hey! We 've verified this expert answer for you, click below to unlock the details :)
At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas molestias excepturi sint occaecati cupiditate non provident, similique sunt in culpa qui officia deserunt mollitia animi, id est laborum et dolorum fuga.
Et harum quidem rerum facilis est et expedita distinctio. Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime placeat facere possimus, omnis voluptas assumenda est, omnis dolor repellendus.
Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus maiores alias consequatur aut perferendis doloribus asperiores repellat.
I got my questions answered at brainly.com in under 10 minutes. Go to brainly.com now for free help!
So just wanted to explore different options through which i can do that,
wanted to evaluate pros and cons of each of them,
and based on that analysis, I will use one.
Had some previous exposure on socket programming, I can look into that.
plz suggest any other ways...
Not the answer you are looking for? Search for more explanations.
IPC would require that both the server and client are processes in the same memory space. If this program is going to run with the client and server on different machines, I don't know of any other good way of doing it than TCP/IP. TCP/IP also works fine if the client and server are on the same machine.
Well, there are a number of different tyoes of sockets.
So the program is going to run on different machines.
My Socket choice, assuming I will be choosing socket programming, would depend on what I use for data transmission,
like if I use TCP/IP, I "need" to use stream sockets,
if I use UDP, I need to use Datagram Sockets.
My first impulse would be to use TCP/IP only as they are more reliable.
(I know UDP has its own advantages)
this limits my choices!
I thought there will be like 10-12 different ways in which I can solve the same problem at hand....
Maybe tailor-suit a new data transmission protocol, best suited for my problem, which has only required advantages of TCP/IP and UDP and any other protocols available... but thats a long shot
Some people use UDP but then set up their own error checking. So they can get more speed than TCP by using a newer error checking algorithm. An example is to use something like the torrent standard over UDP where each chunk is checked for issues.