Thread and Process both do the same thing. ie. parallel jobs done on a CPU. The thread is under the process's control, ie. the programmer can control the thread regard to its priority, memory etc. I am not very sure about multi-threading and process-control under Windows. We have a process control system running on a 8086 based system. It is of Siemens make. It supports 64 threads which are called Tasks in their terminology. Initiation of task, suspending the task, readying the task etc is under the control the program, ie user software. In another computer Data General's M-600, we had multiple processes (max 64), each having a logical address space of 64 kilo bytes. Under each process we can have multiple tasks (I think max 32 tasks). The task control block is in the program's memory space. Intertask communication is pretty simple here. Sharing memory between tasks is simple as the entire memory of the process is under the control of the process. I have used a muti-tasking program under windows. One task continuously communicates with a groupp of microprocessor based controlers over RS-485, and another task processes the read data and does display, storage etc. The program was written in VC++(6.0) . Here the sharing of memory is easy as the entire memory of the process is shared between the tasks(threads). But VB uses something called compartmental multi-threading, meaning each thread has its own compartment of resources.
both process and thread are independent sequence of execution
what are the similarities between basketball and ring-ball
They both are different kinds of air.
what is the similarities between the ulna and the radius
similarities
what are the similarities between network switch and a hub
A thread is a sub process in other words one process can contain multiple threads.
The same metaphor: the difference of a person (thread) and a family (process) A process has at least 1 thread and may have many threads, while 1 thread must live within a process
No.
Basically no difference, except that process can use many threads; thread can use only one.
No. A thread is a part of a process, but a process can not be part of a thread. Processes are always "at the top."
No, a thread can't create aprocess, because the environment of the thread is a part of a process which created this thread.
Execution context within a process is called Thread. Threads run, process does not. Every process starts with one thread.
Process based is much time as comparison as thread based. as well as Thread based application is cost effective. Process based application has its own address space so it take more cost. Alok Gupta. India.
yes, because if process is terminated then its related thread has no work. After completion of process the kernel generates a thread that will cancelled the thread in order to save the time and memory of CPU.
A thread is basically a lightweight process.
synchornisation is the process where more than one thread can be accessed by accesssing the shared object of the class.By syncornisation we can have the communication between threads.if one thread works then another thread automatically stops
The process is the same.