multithread in an application WEB? ??

[AAAAA]

Hi friends,
So that you would use multithread in an application WEB?

Thanks

Cesar

[Egghead]

ya,
"AAAAA" <AA***@hotmail.comwrote in message
news:%2***************@TK2MSFTNGP06.phx.gbl...

>
Hi friends,
So that you would use multithread in an application WEB?

Thanks

Cesar

[Samuel R. Neff]

All web applications are multithreaded by default (each aspx request
is handled by any of a large number of worker threads).

Sam

------------------------------------------------------------
We're hiring! B-Line Medical is seeking .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.
On Thu, 14 Jun 2007 23:19:21 -0500, "AAAAA" <AA***@hotmail.comwrote:

>
Hi friends,
So that you would use multithread in an application WEB?

Thanks

Cesar

[Peter K]

Samuel R. Neff <sa********@nomail.comwrote in
news:6i********************************@4ax.com:

All web applications are multithreaded by default (each aspx request
is handled by any of a large number of worker threads).

But is it correct to say that my aspx/code-behind class is instantiated
anew on each request to it?

Or is it at least guaranteed that the instance of my class won't receive a
second request while it is processing the first request?

Or can I risk that there is only the one instance of my class, and it can
receive a second request while it is still processing the first request?
/Peter

[Jesse Houwing]

* Peter K wrote, On 15-6-2007 10:24:

Samuel R. Neff <sa********@nomail.comwrote in
news:6i********************************@4ax.com:

>All web applications are multithreaded by default (each aspx request
is handled by any of a large number of worker threads).

But is it correct to say that my aspx/code-behind class is instantiated
anew on each request to it?

Or is it at least guaranteed that the instance of my class won't receive a
second request while it is processing the first request?

Or can I risk that there is only the one instance of my class, and it can
receive a second request while it is still processing the first request?
/Peter

A new instance is used for each request. There can be more than one
request to the same page being handled at the same time, so there can be
multiple instances (so avoid the use of static properties & fields).

Jesse

[Allan Ebdrup]

"Jesse Houwing" <je***********@nospam-sogeti.nlwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...

A new instance is used for each request. There can be more than one
request to the same page being handled at the same time, so there can be
multiple instances (so avoid the use of static properties & fields).

Unless you use the appropriate locking on your critical regions.
Static properties & fields can be very usefull.

Kind Regards,
Allan Ebdrup

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

"Peter K" <xd****@hotmail.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...

Samuel R. Neff <sa********@nomail.comwrote in
news:6i********************************@4ax.com:

>All web applications are multithreaded by default (each aspx request
is handled by any of a large number of worker threads).

But is it correct to say that my aspx/code-behind class is instantiated
anew on each request to it?

Yes, that's correct each time a new instance is created and the controls's
values populated based on the state being returned by the page.

Or is it at least guaranteed that the instance of my class won't receive a
second request while it is processing the first request?

Each request will have its own individual instance

[Jesse Houwing]

* Allan Ebdrup wrote, On 15-6-2007 13:53:

"Jesse Houwing" <je***********@nospam-sogeti.nlwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...

>A new instance is used for each request. There can be more than one
request to the same page being handled at the same time, so there can be
multiple instances (so avoid the use of static properties & fields).

Unless you use the appropriate locking on your critical regions.
Static properties & fields can be very usefull.

Agreed. But only if you know what you're doing.