Re: ASP.NET Threading, IIS pipeline and HTTP

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

if you asp.net sessions, then the requests are queued, as session management
is not designed for concurrent access to the same session. you just need to
turn sessions off. note - the browser will limit you to 2 concurrent
requests.

-- bruce (sqlwork.com)


"Rod" <rod@xxxxxxxxxxx> wrote in message
news:Ob2LMuY3GHA.4796@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have a frameset with two frames.
The .aspx page for each frame contains a button with a server click event
handler assigned.
The server code for one button runs a time consuming process, the code for
the second button updates a text field on the same page.

The way I understand it the aspnet_wp process has a thread pool and each
request is assigned to a thread, so what I would expect to happen is that
I could click the button on the page in the first frame, the form would
submit and the time consuming process would start. Then if I clicked the
button on the page in the second frame its page would submit and the text
would be updated concurrently.

This doesn't happen. The request from the second button click seems to be
queued somewhere and isn't processed until the server process for the
first button click has completed.

I'm aware that HTTP 1.1 imposes some restrictions so my Web.Config has a
<system.net>
<connectionManagement>
<add address="*" maxconnection="100"/>
</connectionManagement>
</system.net>
section.

Looking at the network activity I can see the HTTP POST from the second
button click being sent immediately but the code behind page-load handler
never sees it until the first page's processing is complete.

My code doesn't contain any ASPCompat settings or anything else that I
think could affect the way it runs. I'm using .NET 2.0, XP SP2 and IIS
5.1.

Am I missing a Web.Config setting here to get concurrent processing or is
this an IIS pipelining issue or is my understanding of the ASP.NET
threading model completely wrong?



.

Relevant Pages

  • Re: [PHP] Passing variables between pages
    ... tedd wrote: ... The problem was not how to pass variables between requests, but rather how to variables between pages -- as the subject line indicates. ... But here is what I would like you to consider, the next time you are thinking about using sessions to pass variables to the next script, try this technique instead. ...
    (php.general)
  • Re: [PHP] Passing variables between pages
    ... The problem was not how to pass variables between requests, but rather how to variables between pages -- as the subject line indicates. ... But here is what I would like you to consider, the next time you are thinking about using sessions to pass variables to the next script, try this technique instead. ... 3: Passing Variables Between Requests. ...
    (php.general)
  • Re: How hard is socket programming?
    ... As you point out, if there are 10 requests pending, this ... But if you had a concurrent server, ... my multiple cores, it does get faster with faster memory. ...
    (microsoft.public.vc.mfc)
  • Re: control concurrent session
    ... maximum number of concurrent connections to the share. ... > currently i am able to restrict 11 concurrent sessions at the ... >> Vera Noest ... >> MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • [RFC][PATCH 2/2] readahead: avoid page-by-page reads on POSIX_FADV_RANDOM
    ... submit read IO for whatever application requests. ... Note that the random hint is not likely to help random reads performance ... same file descriptor is being concurrent read in another thread. ...
    (Linux-Kernel)