Imagine you and someone else are both creating something out of wood -- maybe you are making a lamp and the other person is making a baseball bat. You both need to use a lathe, but there's only one. That lathe is a resource. The lathe is located inside a room, along with a white board for you to sketch your design and do some calculations on how big to make things. Every hour, on the hour, you get to go in an use the lathe and whiteboard, but only for half an hour. Then you must leave, so you take your partially completed work off the lathe and erase your stuff from the whiteboard and clean up the room and depart. The other person comes in every hour on the half-hour and is under the same rules. As far as each of you is concerned, you are the only one using the room. That's resource sharing.I don't think there is any difference between the task, process and thread. They all are same thing.
I am trying to understand the meaning of following definition for interprocess communication.
"Inter process communication is a process of real time operating system that allow one process to communicate with the another process."
I don't understand how one task/process communicate with the another task/process. I only understand task/process can share the resources like CPU time Or memory.
Now imagine that you are both working on the same project -- maybe you are making the top of the lamp and they are making the bottom of the lamp. You need to know exactly how large the diameter of the bottom of your piece needs to be so that it will match with the top of their piece. But the other person is responsible for determining that diameter (perhaps they have the metal ring that will fit around the joint). So, at some point while they have the room, they write the needed diameter on the white board but they don't erase it when they leave. Now when you come in, it is still there for you to see. That's interprocess communication.