Re: Concurrent processing of ASP.NET pages
- From: "bruce barker \(sqlwork.com\)" <b_r_u_c_e_removeunderscores@xxxxxxxxxxx>
- Date: Fri, 29 Sep 2006 08:45:30 -0700
there are two causes for this.
1) the two browsers are using the same session. say you opened the second
one from IE's new window rather than from the start menu. asp.net serializes
accss to session.
2) IE limits the number of requests to the same server, so will serial the
requests. yucan bump this up in the registry.
-- bruce (sqlwork.com)
"Hitesh" <kathuria.hitesh@xxxxxxxxx> wrote in message
news:1159517391.181840.320320@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We all know that IIS and asp.net are suppose to be muti-threaded
applications running on a pre-emptive multi-tasking model. But, what I
have
found is that under the default installation of ASP.NET, aspx pages get
executed serially. I know that it's easy to say that this can't be
right,
but I have found threads where others have confirmed this same
behavior.
The situation is _very_ easy to reproduce. Simply place two aspx pages
on a
web site, on the one page put some code that will take a bit to execute
(say
a while loop) and on the other page simply put some text (perhaps
"hello").
Now open two browser windows, in the first browser open the long
running
page, now in the second window open the hello page. What you will find
is
that you will not receive the hello page until the long running page
completes and is sent to the browser. The pages are running serially
on the
server!
How does one configure asp.net so that the pages run under a preemptive
multitasking model?
.
- Follow-Ups:
- Re: Concurrent processing of ASP.NET pages
- From: Hitesh
- Re: Concurrent processing of ASP.NET pages
- References:
- Concurrent processing of ASP.NET pages
- From: Hitesh
- Concurrent processing of ASP.NET pages
- Prev by Date: Re: How do you pass credentials from a classic ASP app to ASP.NET 2.0?
- Next by Date: Re: ASP.NET and .NET Framework 2.0
- Previous by thread: Re: Concurrent processing of ASP.NET pages
- Next by thread: Re: Concurrent processing of ASP.NET pages
- Index(es):
Relevant Pages
|
Loading