Question

Different ways in which clients and servers can communicate??

One of the way is through sockets.
I wanted to explore additional options...

Answer 1

My exact problem statement is

Answer 2

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...

Answer 3

Does MySQL server help ?

Answer 4

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.

Answer 5

Well, there are a number of different tyoes of sockets.
http://www.tutorialspoint.com/unix_sockets/what_is_socket.htm

Answer 6

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.
right?

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

Answer 7

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.