Home All Groups Group Topic Archive Search About
Author
24 Mar 2005 8:49 PM
George Medlock
I see all kinds of threading but there is nothing explaining thread.

Author
24 Mar 2005 11:51 PM
John Timney (ASP.NET MVP)
Its a way of running methods at the same time that other methods are
running.  Normally in a single threaded application only 1 method at a time
runs, sequentially usually - so that the code executes from main, through
your code, calling methods one after the other in a top to bottom type of
approach.

Multithreaded applications provide the ability to allow numerous activities
to happen at more or less the same time, so for example the same method or
class can be invoked and can be executing many times in many threads at the
same time and not usually impact the work each is doing.

Best way to understand them is to create a small example for yourself,
theres stacks on the web.

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

Show quoteHide quote
"George Medlock" <georgemedl***@bellsouth.net> wrote in message
news:2SG0e.62124$Q83.57478@bignews5.bellsouth.net...
> I see all kinds of threading but there is nothing explaining thread.
>
>
Author
25 Mar 2005 12:31 AM
Dennis
I'm sure everyone knows that on a single processor machine, the threads don't
run "at the same time".  They are time sliced such that each gets it's turn
at some processor (CPU) time depending on the thread priority.

Show quoteHide quote
"John Timney (ASP.NET MVP)" wrote:

> Its a way of running methods at the same time that other methods are
> running.  Normally in a single threaded application only 1 method at a time
> runs, sequentially usually - so that the code executes from main, through
> your code, calling methods one after the other in a top to bottom type of
> approach.
>
> Multithreaded applications provide the ability to allow numerous activities
> to happen at more or less the same time, so for example the same method or
> class can be invoked and can be executing many times in many threads at the
> same time and not usually impact the work each is doing.
>
> Best way to understand them is to create a small example for yourself,
> theres stacks on the web.
>
> --
> Regards
>
> John Timney
> ASP.NET MVP
> Microsoft Regional Director
>
> "George Medlock" <georgemedl***@bellsouth.net> wrote in message
> news:2SG0e.62124$Q83.57478@bignews5.bellsouth.net...
> > I see all kinds of threading but there is nothing explaining thread.
> >
> >
>
>
>
Author
25 Mar 2005 9:07 AM
Cor Ligthert
George,

Multithreading is using assynchronous parallel processes. Where that can be
with more or hyperthreading processors doing computercommands real parallel
and with a single processor doing the computercommands in a more sequential
way (however sliced) one by one.

I hope this gives an idea.

Cor
Author
25 Mar 2005 7:28 PM
John Timney (ASP.NET MVP)
Its a description designed for someone who doesn't understand threading,
hence the staement more or less the same time.

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

Show quoteHide quote
"Dennis" <Den***@discussions.microsoft.com> wrote in message
news:83D9F008-F76F-4DFF-850E-7012A8AB6400@microsoft.com...
> I'm sure everyone knows that on a single processor machine, the threads
don't
> run "at the same time".  They are time sliced such that each gets it's
turn
> at some processor (CPU) time depending on the thread priority.
>
> "John Timney (ASP.NET MVP)" wrote:
>
> > Its a way of running methods at the same time that other methods are
> > running.  Normally in a single threaded application only 1 method at a
time
> > runs, sequentially usually - so that the code executes from main,
through
> > your code, calling methods one after the other in a top to bottom type
of
> > approach.
> >
> > Multithreaded applications provide the ability to allow numerous
activities
> > to happen at more or less the same time, so for example the same method
or
> > class can be invoked and can be executing many times in many threads at
the
> > same time and not usually impact the work each is doing.
> >
> > Best way to understand them is to create a small example for yourself,
> > theres stacks on the web.
> >
> > --
> > Regards
> >
> > John Timney
> > ASP.NET MVP
> > Microsoft Regional Director
> >
> > "George Medlock" <georgemedl***@bellsouth.net> wrote in message
> > news:2SG0e.62124$Q83.57478@bignews5.bellsouth.net...
> > > I see all kinds of threading but there is nothing explaining thread.
> > >
> > >
> >
> >
> >