Asp.net multithreading (favorites)

1. Analysis http://developer.51cto.com/art/200907/138426.htm of ASP. NET multithreading technology

2. (original) asp.net example of displaying the task execution progress on the client using a multi-thread task for a long time (2)

3. Multithread sample http://blog.csdn.net/gloomyboyo/archive/2006/08/09/1042187.aspx

4. Summary: several methods of Thread Synchronization in C #

5. c # thread synchronization: details about lock, monitor, synchronization events, wait handles, and mutex

6. Thread Synchronization example http://blog.csdn.net/zhoufoxcn/archive/2008/05/17/2453803.aspx

7. Thread Synchronization and deadlock http://developer.51cto.com/art/200908/141606.htm

8 .. NET multi-thread lock mechanism http://blog.csdn.net/gongdalaoying/archive/2009/02/06/3863357.aspx

9.

Differences between processes and threads
Processes and threads are the basic units for running programs that the operating system understands. The system uses this basic unit to realize the system's concurrency for applications. The difference between a process and a thread is:

In short, a program has at least one process, and a process has at least one thread.

The thread division scale is smaller than the process, making the multi-thread program highly concurrent.

In addition, the process has independent memory units during execution, and multiple threads share the memory, which greatly improves the program running efficiency.

The execution process of a thread is different from that of a process. Each Independent thread has a program running entry, sequence execution sequence, and program exit. But the thread cannot be executed independently. It must exist in the application and the application provides multiple thread execution control.

Logically, multithreading means that multiple execution parts in an application can be executed simultaneously. However, the operating system does not view multiple threads as multiple independent applications to implement process scheduling, management, and resource allocation. This is an important difference between processes and threads.

A process is a running activity of a program with certain independent functions. A process is an independent unit for the system to allocate and schedule resources.

A thread is an entity of a process. It is the basic unit for CPU scheduling and scheduling. It is smaller than a process and can run independently. the thread itself basically does not have system resources, and only has a few resources (such as program counters, a set of registers and stacks) that are essential for running ), however, it can share all resources of a process with other threads of the same process.

One thread can create and cancel another thread, and multiple threads in the same process can be concurrently executed.

The main difference between processes and threads is that they are different operating system resource management methods. A process has an independent address space. After a process crashes, it will not affect other processes in the protection mode, but the thread is only a different execution path in the process. A thread has its own stack and local variables, but there is no separate address space between threads. If a thread dies, the whole process dies. Therefore, multi-process programs are more robust than multi-threaded programs, however, during process switching, resources are consumed and the efficiency is lower. But for some concurrent operations that require simultaneous and shared variables, you can only use threads, not processes. If you are interested, I suggest you take a look at the modern operating system or the design and implementation of the operating system. Make it clear about the problem.

This article from the CSDN blog, reproduced please indicate the source: http://blog.csdn.net/andy6355/archive/2008/06/03/2506171.aspx