More on Threads and Processes
This [article][1] about what are threads and first defines a procces reads 

"The operating system provides this virtualisation. Processes execute modules of code. 
These may be disjoint; in the sense that, the executable modules of code comprising Windows Explorer 
and Microsoft Word are disjoint. However, they may also be shared, as in the case of DLL's, the code 
for which is typically being executed in the context of many different processes, often simultaneously. 
The execution speed or ordering of processes is normally independent of one another: Microsoft word does 
not stop opening a document just because the print spooler is currently sending something to the printer! "

I explain the article reads that "just because the print spooler is currently sending something to the printer! "

I got a respocne that "It doesn't stop popening the doc just becuase the print spool 
because opening a document and spooling the printer are different processes"

it was further explained that 

"yes basically two programs may be using one DLL
but they are still separate processes
so one process may have multiple threads
like when you go to task manager, you can look at processes
Each process gets their own turn on the CPU"


I wanted more clarification about it and got

"They are just saying that the DLL can be executed by multiple things simultaneously.
The code for a DLL is typically being executed in the context of many different processes, often simultaneously
that's the key line"

and "two processes both using the same DLL (lets say "interpretdocument.dll") can both execute at the same time. they do not have to wait for one to "finish" with the dll
in many other cases things that share resources would have to do that. One does not stop the other"

Then I explained it is not technically running simultaneously but flip flopping


and finally got to the point I didin't get: the individual responded:

"right but it doesn't hold the resource if it did that then the entire process of opening the document would have to complete, then it would release the DLL then the printer could start using it
like trying to rename a document when its open
I assume... you're reading the book, not me :)"


My question is, what does this mean "but it doesn't hold the resources, is the resource the DLL or the .doc file, and why was it emphasized? they share the resource? 


  [1]: http://www.seti.net/SETINet/Other/Threads/Chap%201/Ch1.htm
More on Threads and Processes
===

This [article][1] about what are threads and first defines a procces reads 

"The operating system provides this virtualisation. Processes execute modules of code. 
These may be disjoint; in the sense that, the executable modules of code comprising Windows Explorer 
and Microsoft Word are disjoint. However, they may also be shared, as in the case of DLL's, the code 
for which is typically being executed in the context of many different processes, often simultaneously. 
The execution speed or ordering of processes is normally independent of one another: Microsoft word does 
not stop opening a document just because the print spooler is currently sending something to the printer! "

I explain the article reads that "just because the print spooler is currently sending something to the printer! "

I got a respocne that "It doesn't stop popening the doc just becuase the print spool 
because opening a document and spooling the printer are different processes"

it was further explained that 

"yes basically two programs may be using one DLL
but they are still separate processes
so one process may have multiple threads
like when you go to task manager, you can look at processes
Each process gets their own turn on the CPU"


I wanted more clarification about it and got

"They are just saying that the DLL can be executed by multiple things simultaneously.
The code for a DLL is typically being executed in the context of many different processes, often simultaneously
that's the key line"

and "two processes both using the same DLL (lets say "interpretdocument.dll") can both execute at the same time. they do not have to wait for one to "finish" with the dll
in many other cases things that share resources would have to do that. One does not stop the other"

Then I explained it is not technically running simultaneously but flip flopping


and finally got to the point I didin't get: the individual responded:

"right but it doesn't hold the resource if it did that then the entire process of opening the document would have to complete, then it would release the DLL then the printer could start using it
like trying to rename a document when its open
I assume... you're reading the book, not me :)"


My question is, what does this mean "but it doesn't hold the resources, is the resource the DLL or the .doc file, and why was it emphasized? they share the resource? 


  [1]: http://www.seti.net/SETINet/Other/Threads/Chap%201/Ch1.htm