🚀 go-pugleaf

Hi Net Gurus,
 
could any one tell me the advantages of "Socket Based interprocess
communication" over "Remote Procedure Call based interprocess communication"?

My application program runs on the top of the packet layer. It communicates 
with a X.25 switch. The communication between switch and application programm
is based on 'BSD Socket based communication'.

I summarize it in the following steps- 

1. I open a socket in X.25 domain (i am using SunNet X.25 software).

2. Pass the address of remote switch to the socket.

3. send some data (e.g. 'stat' command for the switch which gives all the 
statstical information from the switch). 

4. receive the output (e.g. output of 'stat' command which is parameter values 
from the switch).

             ----------------------------------------------------------

My questions are: 

1.why and when the socket based communication is used?

2.Why always RPC based communication is prefered over socket based 
communication is prefered?

3. Is it possible to implement a 'Client-Server' model using  sockets? if yes,
can i call 'My-application-program=X.25-switch' (as given in steps 1-4) as
a 'cleint=server' model?


Any pointers/hints..? Thanks very much for reading this. I will welcome any
concern information.

Please ..send your answers by email to me.

- Bharat

(bharat@ccvax.ucd.ie)