IPC : Named Pipes, RPC and Sockets etc.

From: MIcrosft_Public_SQLSERVER (araskas100_at_yahoo.com)
Date: 02/05/05 

Date: 5 Feb 2005 14:40:30 -0800

In SQL Server BOL it it is mentioned that Named Pipes, RPC and Sockets
are all IPC mechanisms. Basically I want to understand -
1. What are these IPC mechanisms?
2. Are they common to other Operating Systems?
3. RPC, Named Pipes, Sockets, local pipes, anonymous pipes - are these
some standards or protocols or code libraries?
4. Are these essential fro client-server environment? Which one came
first, ipc or client-server computing?
Is it possible to have client-server computing without IPC?
5. What is the difference between TCP/IP sockets, windows sockets and
Winsock?
6. When I open a web browser and connect to a web site I am using
TCP/IP for sure, but are there any sockets or IPC also involved in this
connection?

These are some of the things I would like to understand. I appreciate
if someone could direct me to any resources, or books that cover these
topics.

Thanks

Relevant Pages

  • Re: Interprocess Communication
    ... The CH2 child will be the controlling process. ... Once control is completed two CH1 children will be communicating in both ... You can do dup/popen etc. but I find sockets simpler with C. ... I thought I would do the additional child using IPC ...
    (comp.os.linux.misc)
  • Sockets vs. Named Pipes (2)
    ... I'm comparing two IPC ... I want to solve next problem: secure IPC connection to process under system ... firewall administrator configured local firewall to pass all requests ... Does anyone know if the same problem is actual for Named Pipes? ...
    (microsoft.public.security)
  • Sockets vs. Named Pipes (2)
    ... I'm comparing two IPC ... I want to solve next problem: secure IPC connection to process under system ... firewall administrator configured local firewall to pass all requests ... Does anyone know if the same problem is actual for Named Pipes? ...
    (microsoft.public.win2000.security)
  • authentication (SRP*, DH, TLS)
    ... sockets instead of Named Pipes for IPC. ... Now I'm trying to recreate that with the tcp sockets version. ... "GNU Library General Public License" under. ... not sure (I'll assume this is LGPL) this is legal as LGPL ...
    (sci.crypt)
  • Re: Communications Between Program and Controlling Program
    ... Named pipes if you are working within a single Windows domain (or domains with mutual ... Sockets if you need to work across multiple domains. ... Also, no matter what your protocol is, make sure that you can handle multiple startup ...
    (microsoft.public.vc.mfc)