Scribd
Upload
2 views12 pages

IPC

Interpersonal Communication (IPC) refers to various methods by which computer programs communicate, similar to human communication methods. IPC enables processes to share information, collaborate on tasks, and utilize shared resources efficiently, with techniques including message passing, shared memory, pipes, message queues, sockets, and signals. Best practices for IPC involve security considerations, performance optimization, and adherence to design guidelines.

Uploaded by

regina
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views12 pages

IPC

Interpersonal Communication (IPC) refers to various methods by which computer programs communicate, similar to human communication methods. IPC enables processes to share information, collaborate on tasks, and utilize shared resources efficiently, with techniques including message passing, shared memory, pipes, message queues, sockets, and signals. Best practices for IPC involve security considerations, performance optimization, and adherence to design guidelines.

Uploaded by

regina
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

INTERPERSONAL

COMMUNICATION

Understanding IPC

Think of IPC as different ways computer


programs talk to each other, just like how
people use phones, text messages, or
face-to-face conversations to
communicate.
Page 01
What is IPC?
Processes are like workers in different offices who need to
share information
By default, processes are isolated (like rooms with no
windows or doors)
IPC creates safe "doorways" for processes to:
Share information
Work together on tasks
Use shared resources without conflicts
Just like how different departments in a company share
information through meetings, emails, or documents

Page 02
WHY DO WE NEED IPC?

INFORMATION SHARING RESOURCE SHARING PERFORMANCE BENEFITS

Example: Text editor and Like a shared printer in an Like a shared printer in an
spell checker working office office
together Multiple programs need to Multiple programs need to
Editor sends text to spell print print
checker IPC manages who uses the IPC manages who uses the
Spell checker returns printer and when printer and when
corrections
Without IPC, these
programs couldn't work
together
Page 03
MESSAGE PASSING
Message passing is like sending letters through a
postal system:

Direct Communication
Process A talks directly to Process B
Like making a phone call to a specific person
Example: Game client sending moves to game server
out by individuals or teams and is designed to achieve specific
outcomes within a set timeframe.

Indirect Communication
Processes leave messages in a shared location
Like a mailbox at the post office
Other processes pick up their messages
Example: Print jobs going to a printer queue
Page 05
SHARED MEMORY
Think of shared memory as a shared
whiteboard in an office

System creates a special memory region


Multiple processes can read/write here
Fastest form of IPC - no need to copy data
Example: Video editing software
One process writes video frames
Another process applies filters
Third process handles display
All access same data without copying
Page 05
PIPES
Pipes are like water pipes, but for
data

ORDINARY PIPES NAMED PIPES


Works only between related Works between any
processes processes
Like a private family conversation Like a public bulletin
board
Example:
Example:
Unix command "ls | grep "file""
Game server broadcasting
ls sends output to pipe
updates
grep reads from pipe
One-way data flow Page 06
MESSAGE QUEUES
Like a take-a-number system at a deli counter:

Messages have types (like priority numbers)


First in, first out order
Messages wait until received

Example:
Print spooler system
Applications send print jobs
Jobs wait in queue
Printer processes one job at a time
Jobs have priority levels
Page 07
SOCKETS
Like phone lines for processes:
Can work across different computers
Two-way communication
Types:
TCP: Like a phone call (reliable)
UDP: Like a postcard (fast but less reliable)
Examples:
Web browsers talking to servers
Online games
Chat applications

Page 08
SIGNALS
Like emergency notifications or quick gestures:
One process sends pre-defined signal
Receiving process must handle or ignore it
Examples:
Ctrl+C to stop a program (SIGINT)
System asking program to close
(SIGTERM)
Force-stopping a program (SIGKILL)

Page 09
COMPARISON OF IPC METHODS

Page 09
IPC BEST PRACTICES
SECURITY CONSIDERATIONS PERFORMANCE OPTIMIZATION DESIGN GUIDELINES

Access control Minimize data copying Keep it simple


Data validation Choose appropriate Document protocols
Resource cleanup mechanism Plan for scalability
Handle errors properly

Page 03
IPC

THANK YOU
Page 10

You might also like