difference b/w thread based and use based testing
-> Difference between process based and thread based multitasking: 1) threads share the same address space where as process doesn't. 2) context switching between threads is usually less expensive than between processes. 3) cost of communication between threads is relatively low.
To calculate the depth of a thread, measure the distance from the crest (top) to the root (bottom) of the thread. This can be done using a thread gauge or caliper. The depth can also be determined by subtracting the root diameter from the major diameter and dividing the result by 2, as thread depth is half the difference between these two diameters. For standard threads, the depth can be found using specific formulas based on the thread profile, such as for triangular threads.
"A thread is the smallest unit of execution" single os can have multiple threads running thereby creating a multithreading environment. Each thread has a priority based on which the process is executed.
Hsusbsbsn
The difference between asset based lending and cash flow based lending is that asset based uses things you own, while cash flow means what you earn in a month.
The difference between Canada's government and Rwanda's government is that Canada's is based on Democracy while Rwanda's government is based on Democracy and pride.
SQL is a query based language that is used to manipulate data stored in a database while other languages process data.
Main difference is that , that the auto_t is electrical based while the other t is based on mutual inductance.
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.
One is number based
properties are based on axioms